sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
sb> Packages typically want to know two specific things about the
external
sb> environment.
There is also the
4. Package needs to have specific code eval'ed at startup time, i.e.
the autoloads.
Exactly right. There is a problem currently with associated
executables: you really want only the package, which knows about its
executables, to be able to execute them. You don't want to add them
to exec-path and PATH where potentially everyone gets affected. This
is also a great source of confusion currently, for example with the
tm-associated scripts.
Indeed.
I think especially this last bit will have to change: I would want
a
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 not
even know which package it is in? Or we will just make the requirement
that each set of lisp files with data files needs to be in its own
package?
Jan