Stephen J. Turnbull wrote:
This is by design. --with-package-prefix is designed to simplify
package-path specification.
... and actually makes things more complicated. As you mention later
in your message, I discovered the existence of --package-prefix, and
interpreted it as a simpler way to precise the standard package location,
avoiding the need to specify site, xemacs and mule locations by hand with
--package-path. So I went from
--package-path=/usr/local/share/xemacs/site-packages:\
/usr/local/share/xemacs/mule-packages:\
/usr/local/share/xemacs/xemacs-packages
to
--with-package-prefix=/usr/local/share/xemacs
Note that my own (~/.xemacs) package directory isn't specified anywhere. Now
you're telling me that these two options silently affect the user's package
path in a different way /by design/ ?? Well, I think the design is severely
broken then.
FWIW, I don't see much point in arguing about the defaults.
Uh, if you go that way, I don't see much point in arguing about
anything then.
IMHO the package path specification stuff is basically broken from
the point
of view of allowing users to say what they want simply.
This, we agree on :-)
--
Didier Verna, didier(a)lrde.epita.fr,
http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-BicĂȘtre, France Fax.+33 (1) 53 14 59 22 didier(a)xemacs.org