Tollef Fog Heen <tfheen@raw.no> wrote:
> * Peter S Galbraith
>
> | AFAIK, you need to depend on emacs itself (and not emacs-common) if you
> | byte-compile it. I _think_ stuff can break if you don't, but I'm vague
> | on why. Search the debian-emacsen archives. I split off a package
> | because of that issue a while back, but the seperate -el package is 62KB.
>
> I don't think you need to, because of the way emacsen have their
> post-inst-hooks where all the packages which can be used with them are
> byte-compiled.
I found it:
http://lists.debian.org/debian-emacsen/2002/debian-emacsen-200202/msg00041.html
http://lists.debian.org/debian-emacsen/2002/debian-emacsen-200202/msg00050.html
and:
http://www.debian.org/doc/packaging-manuals/debian-emacs-policy
D) Each add-on package must declare relevant dependencies on other
packages (including other add-on packages). Note that add-on
packages should not depend on emacsen-common directly, but rather
on either the virtual package "emacsen" (see below), or some
appropriate combination of flavors (i.e. Depends: emacs21 |
emacs10).
> And as you write below, byte-compiling a 4k file is
> probably not worth the effort.
That's what I think anyway.
Peter