> * gettext does not need a Depends, it just needs a better > emacs-package-install implementation, namely, one that does not fail > if emacsen-common has not been configured yet.
If we can figure out a way that we're *sure* will work right, then I'm OK with changing emacsen-common so that add-on packages don't have to depend on it, but I want this considered carefully. I'm satisfied (as mentioned in my reply to Toby) that we don't have to worry about the install/remove scripts being run before the add-on package is used, but I'd like everyone to help me think through any other possible complications. For example, is dpkg OK with a package foo containing files in directories that are owned by a package that foo doesn't depend on? Along those same lines what happens if emacsen-common is installed, gettext is installed, emacs21 is installed, and emacs21 is removed and emacsen-common is removed? The new (relaxed) dependency arrangement would allow that. Is that OK? Thanks -- 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
