Re: [issue] XEmacs 21.5 can't find packages
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.
I guess I'm not clear on what is meant by "relocatable" given that
"run-in-place" works with --with-prefix=yes.
All other absolutely specified paths *will* get compiled in. And no,
we
don't want it to conflict, because that would prevent you from doing
what you were trying to do do. (You should do --with-prefix=no
--with-late-packages=<...>, if I understand your goal correctly.)
> "Easy"? I can never remember the syntax. :-P
It's certainly
> "flexible" enough though! :-)
:-)
Hints on what kind of info make it easier are appreciated.
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.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta