On Tue, Jun 06, 2006 at 12:03:04PM +0200, Frank Küster wrote: > Package: emacsen-common > Version: 1.4.16 > Severity: important > > Currently when an emacs is installed, it executes > > /usr/lib/emacsen-common/packages/install/<pkg> <flavor> <others> > > for each <pkg> it finds. However, when emacs is installed in one dpkg > run together with an add-on package, and this add-on package has an > additional dependency, this will in many cases fail. > > For example, auctex Depends: gs-gpl | gs, and uses gs in its install > script. Thus, if I say > > apt-get install emacs21 auctex > > then emacs21 will sometimes be configured before gs-gpl is configured, > and configuring emacs will fail because > /usr/lib/emacsen-common/packages/install/auctex fails. > > One possible solution would be to require that every package register > somewhere (probably best by touching some file named after it) that it > has once been configured successfully for any emacs. If an emacs main > package is installed, it will execute the install scripts only for > packages which have already registered themselves. Otherwise running > the install script is left to those packages' postinst script.
Looking into emacsen-common bugs, Frank, note that this should no longer be an issue since there is now a single ghostscript package and not different gs alternatives. Anyway, I think this problem, in case it reappears, is better addressed from auctex emacsen-install file, by checking that there is a gs available and pointing to something real. -- Agustin
