greg(a)alphatech.com wrote:
If you have 2 versions of a package (eg, the one that the sys admin
downloaded with your SUMO binary and a newer one you've installed in
~/.xemacs/packages) you get these irritating warnings on startup:
(1) (warning/warning) Autoload error in:
/home/greg/.xemacs/packages/lisp/pcl-cvs/auto-autoloads:
Already loaded
Isn't this an expected usage, one which should not spew warnings?
I'd say that this should not be happening. I'd also go further and
say that:
* Packages in ~/.xemacs/packages should probably take precedence over
any system-installed ones. As it is, it appears that the system-
installed ones are loaded before those in ~/.xemacs/packages.
* There needs to be some kind of package version/revision that is stored
when a package is loaded (hmm, just noticed that this data already
exists, but we need to use it). That way, a more informative error
message could be output (or not at all), if another version of the
same package is encountered:
+ If the two packages have the same version/revision, a warning is
output about the duplicate package (or nothing is output at all).
+ If the first (user's) package is newer than the second (system's)
package, a warning is output (or nothing at all). If a warning is
output, it must be easily suppressable.
+ If the first (user's) package is older than the second (system's)
package, an error is output (???).
I think everything that's needed already exists. We just need to
write some elisp (write a function that compares version #s with those
stored in packages-package-list, and modify fixup-autoload-buffer to
use the function).
--
Darryl Okahata
darrylo(a)sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.