Re: Bug#65320: gettext: fails on postinst
Santiago Vila <sanvila@unex.es> writes:
> 1. Make gettext to Depend on emacsen-common. The wrong thing to do, IMHO.
> You can use gettext without emacs if you want, and you should not be
> forced to install software you don't really need.
or
> 3. Make "emacs-package-install" smarter, so that it does whatever
> configuration stuff is needed for it to work properly even if
> emacsen-common has not been configured first. I think this is the way
> to go, so I'm reassigning this bug to the emacsen-common package.
>
> BTW: You will find a more detailed analysis about this in the logs for
> Bug #48681. I really think making "emacs-package-install" smarter is
> not very difficult in this case.
These are the two best options, but I'm *really* hesitant to try and
guarantee that emacsen-common will work properly before it has been
configured. This means second-guessing the whole package
installation/dependency process and committing to some guarantees that
might make development (or redesign of emacsen policy) a lot harder
later on.
How hard would it be for gettext to just provide a gettext-el package
and have that depend on emacsen as per policy?
I may be over-concerned here, but trying to guarantee that a package
is functional before it's pre/postinst scripts have run seems like
asking for trouble.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
Reply to: