reassign 65320 gettext thanks (Santiago, if you haven't been following this lately, check the bug log, and/or the debian-emacsen list. Thanks.)
Toby Speight <[EMAIL PROTECTED]> writes: > Rob> If this were in fact "safe", then we could think about changing > Rob> debian-emacs-policy to fully eliminate the requirement that packages > Rob> that have emacs components *depend* on emacsen, but instead they > Rob> just check for /usr/lib/emacsen-common/emacs-package-install, and if > Rob> found, run it. This is certainly more flexible, but I'm wondering > Rob> if there are nasties that I'm overlooking. > > What happens if emacsen is installed *after* package 'foo' that uses > it? AIUI, foo won't get its emacs components configured at all then. I think you may have hit the nail on the head. I wasn't thinking about the fact that emacsen-common doesn't re-run all the scripts when it itself is installed. This is why I'm very hesitant to go back and relax restrictions I put into debian-emacs-policy initially. It's complicated, and easy to get wrong. It took a lot of head-scratching to get things "right" originally, and I don't want to change things without being really careful that we're not breaking previous assumptions. So I guess we're back to the original question -- could we just add a gettext-el package that depends on emacsen (or whatever combination of emacs pkgs gettext supports -- see policy for Depends: details)? -- 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
