>>>> "vin" == Vin Shelton <acs(a)xemacs.org>
writes:
vin> Attached is a patch which allows 21.5 to find a package tree
vin> in ../xemacs-packages.
You mean this?
... -+- {bin,src}/xemacs <---- executable
|
+- site-packages
|
+- mule-packages
|
+- xemacs-packages
AFAIK that's the way Mike configures his own installation, I'm pretty
sure that works.
Or do you mean this?
... -+- xemacs-$version/{bin,src}/xemacs <---- executable
|
+- site-packages
|
+- mule-packages
|
+- xemacs-packages
As far as I know that's the style that Ben uses, and Mike recently
ripped it out of the standard configuration, although you can still
use --with-late-packages. I do not like that style, I think it's
unclean. "site-packages", especially, is the kind of generic name
used by many scripting languages, and should be prefixed by something
that indicates both that it's part of XEmacs and that it is sibling to
{mule,xemacs}-packages.
I strongly prefer this "two-root" style:
... -+- xemacs-$version/{bin,src}/xemacs <---- executable
... -+- $packages -+- site-packages
|
+- mule-packages
|
+- xemacs-packages
For runtime detection, of course a one-root style is necessary, in
which case I think this is appropriate:
... -+- xemacs-$version/{bin,src}/xemacs <---- executable
|
+- $packages -+- site-packages
|
+- mule-packages
|
+- xemacs-packages
Note the similarity of the above to the current Unix installation
under $prefix/lib with $packages == xemacs.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.