Re: [issue] XEmacs 21.5 can't find packages
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Michael Sperber writes:
> I'm totally amenable to that, but it's not what --with-prefix=no does -
> that does exactly what it advertises, namely:
>
> --with-prefix=no Don't compile the value for `prefix' into the
> executable.
The whole thing is very confusing though. I think I do have it
straight, but "Don't compile the value for prefix", and "make a
relocatable package" are quite different.
That's right - here's the relationship: You can use "Don't compile the
value for prefix" to "make a relocatable package".
I guess I'm not clear on what is meant by "relocatable"
given that
"run-in-place" works with --with-prefix=yes.
Run-in-place is not the same "relocatable", and there's very specific
code to deal with this case.
For starters, I think we should settle on a specific set of options
for configuring package paths, deprecate the rest ASAP, and get rid of
them in the next public release. I think probably the "early",
"late", "last" trio is easiest to understand the effects, and
"typically correspond to 'personal', 'system', and 'legacy'
=
'fallback' packages" as the explanation.
Basically, I believe people should only ever configure "late", so my
recommendation would be to get rid of the "early" and "last" options
and
lose the "late". Acceptable?
--
Regards,
Mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta