Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org:
sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr.
sb> Packages typically want to know two specific things
about the external
There is also the
4. Package needs to have specific code eval'ed at startup time,
> I think especially this last bit will have to change: I would
> package to identify itself (implicitly or explicitly) when asking for
> the location of its associated files.
Hmm.. isn't the problem here that a particular lisp file might
even know which package it is in?
Or care. These kinds of lisp files are currently packaged together in
Or we will just make the requirement that each set of lisp files
with data files needs to be in its own package?
This is current practice. In addition to data files, add manuals and