On Fri, Feb 02, 2007 at 08:35:32AM +0100, Stephan Suerken wrote: > On Thu, 2007-02-01 at 20:48 -0800, Steve Langasek wrote:
> > > * postrm|inst: Check for update-modules before calling. > > > Fixes: "gom: postinst fails: line 21: update-modules: command not > > > found", thanks to Lucas Nussbaum (Closes: #408243). > > Why is this the right fix? More specifically -- if gom depends on > > update-modules being called for proper operation, why doesn't gom have a > > dependency on module-init-tools, and if it doesn't need update-modules for > > proper operation, why does it call it at all? > > I can't see anything in the contents of the gom package that explains why > > update-modules should be called. > The only reason for calling this is the - optional (see auto_init > in /etc/default/gom) - feature to recover mixer settings via gom > automatically when the module is loaded. Um, what module? gom doesn't ship any modules and it doesn't ship any conffiles under /etc/modprobe.d, so what exactly is calling update-modules supposed to do for gom? > I guess for the future, this feature may be removed entirely for > simplicity And for correctness, AFAICS. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
