Re: packages again

andy> For instance the mail-lib that was downloaded was version andy> 1.12 but the _pkg.el for mail-lib in andy> /usr/gnu/lib/xemacs/packages/lisp/mail-lib is v 1.09. ms> The package-admin-add-...-package functions do this to ms> determine where to install: ms> (setq pkg-dir (car (last late-packages))) ms> So you should look at `late-packages'. I don't really feel ms> comfortable with this, but there's generally not a good ms> solution to the problem that packages are searched along a ms> *path* but have to be installed into a *directory*. Here's a guess at the rationale for that choice. If the sysadmin has modified a standard package, then they install that up front in the late-packages path and the automated update procedures thus don't override the localized package with the latest released version. Close enough? Sounds to me like Andy may have a shadow there. This would be detected at build time, but do the package-admin-add-...-package functions check for shadows too?