Re: auto-autoloads errors

Didier Verna writes: I think this is mildly wrong. The idea of {xemacs,mule,site}-packages is to support a partition of available packages. Some versions of XEmacs (ie, --without-mule) will ignore the mule-packages hierarchy. All versions of PUI should ignore the site-packages hierarchy by default (since there's no default place to download site-packages from). You could argue that this is a design bug in the package system, and I'm not prepared to back up my intuition with logic. But unless you've got a weapon loaded with high-calibre code, I think Mike will win the firefight ... ;-) If you want your updated packages in a system hierarchy, then you IMHO should have multiple system paths ending in xemacs-packages. (I don't know for sure if this is supported by ./configure, but I think that --with-late-packages=/usr/local/share/xemacs:/usr/local/share/xemacs-sumo should work, and configure PUI to work with hierarchies in .../xemacs.) Alternatively, you could abuse --with-last-packages for the SUMO. (Originally --with-last-packages was intended to point to the top-level of an XEmacs 20 installation in lieu of a SUMO. This is also one reason why the package system was designed as {etc,lisp}/$PKG instead of $PKG/{etc,lisp}.) I would say that "own" packages belong in site-packages. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta