0> In article <[EMAIL PROTECTED]>, 0> Rob L. Browning <URL:mailto:[EMAIL PROTECTED]> ("Rob") wrote:
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.
