> 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.
I'm confused.
I'd think most packages _already_ check for
/usr/lib/emacsen-common/emacs-package-install before running, at least
if they use debhelper:
# Automatically added by dh_installemacsen
if [ "$1" = "configure" -a -x /usr/lib/emacsen-common/emacs-package-install ]
then
/usr/lib/emacsen-common/emacs-package-install gri
fi
Also, when I install a new flavour of Emacs, all the elisp files of
add-on package get byte-compiled correctly. So I think this is okay.
What am I missing?
Thanks,
Peter
