So, with respect to the primary concern, at the moment, I lean against putting any of the site-lisp directories at the end of the load-path.
Upstream emacs places all of the site-lisp directories before any of the emacs-version-specific directories, and I'd like to avoid diverging any further from upstream on that point if we can. I wonder if a preferable solution might be to have some directory for add-on packages to place their code that's not in the load-path, and then the packages could just symlink themselves into the appropriate flavors. i.e. perhaps gnus could have put its code into /usr/share/gnus/ (or whatever) and then symlinked itself into the appropriate site-lisp directories (not emacs21's). Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
