Michael Sperber writes:
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
> I don't have time to root around in the package generation stuff to do
> a blame, but either you forgot you did it or somebody else beat you to
> it. ;-) I don't really see how you can improve on the above, either
> for real packages or for fake ones.
The idea was to detect shadow packages, and to include only one version
of a shadowed package in the various paths. That's doable, I believe.
You could do that, but make sure you keep the error somehow.
I think one simple approach would be to catch this error, and remove
this file's directory from load-path.
However, I'm dubious that this would really make a big difference.
Except for the $package-autoloads feature, *packages don't know their
own names*. I don't see how you can reliably detect non-packages (ie,
collections of libraries that don't conform to our protocols).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta