Stefan Monnier <[EMAIL PROTECTED]> writes: > That looks OK. If install.el does its job properly it will > - untar this into the user's elisp repository (~/lib/emacs or ~/share/emacs > if I were to choose). > - build the .elc and .info files. > - construct a "autoloads" file that contains the relevant autoloads, as well > as commands to adjust load-path and Info-directory-path. > - add a line in the user's .emacs to load this autoloads file. > > The first 3 steps are the installation proper. The last step is > the activation. This separation is important in case the installation is > made by the sysadmin into /usr/local/lib/emacs. The separation is also > important in case you want to install several different versions of > a package (since usually only one of those versions can be loaded in > a given Emacs session at a time).
One common operation when creating package files for various distributions (probably including XEmacs packages) is to install stuff not into the detected tree, say /usr/share/emacs/site-lisp, but rather into /tmp/rpm-34563/usr/share/emacs/site-lisp or similar, while having all files in that location refer to the _ultimate_ target instead of this temporary tree. Would install.el be comfortable with that kind of operation? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ auctex-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/auctex-devel
