On Mon, 2005-10-31 at 09:46 +0100, Didier Verna wrote:
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.
What's the point of with-package-prefix, if ~/.xemacs cannot be
specified with it? The following design would be much more usefule:
--with-package-path as now
--with-package-prefix would automatically include
~/.xemacs(/xemacs-packages) OR
--with-packages-prefixes (or something like that) to allow specifying
multiple prefixes, something like /usr/local/share/xemacs:/local/xemacs