[Patch21.5] Find a relative package root at runtime

[Vin Shelton]

(Moved to xemacs-beta.)

On 3/1/06, Stephen J. Turnbull <stephen at xemacs.org> wrote:
> >>>>> "vin" == Vin Shelton <acs at 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

Sorry I was skimpy on the details.   We went over this in December for
21.4, so I thought everyone would understand what I meant.  Here's
what I mean:

ls c:\Program Files\XEmacs  ==>
XEmacs-21.4.19/  XEmacs-21.5-b25/  mule-packages/  site-packages/ 
xemacs-packages/

This is the windows default layout.  (I think it corresponds to #2
above.)  It's easy to support this using the PACKAGE_PREFIX setting in
config.inc, but this layout requires runtime support if you want to be
able to create a setup kit that you can install anywhere.

> 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.

Yes, we could add an additional 'packages' layer that subsumes all the
packages.   In fact, that's how I had the original 21.4.18 setup kits
laid out.  My only concern would be getting current users of the
Windows setup kit over the transition.

  - Vin