On Fri, 2003-01-03 at 11:22, Michael Sperber [Mr. Preprocessor] wrote:
>>>>> "Ville" == Ville Skytt
Ville> Hmm, while looking at the newest RH Rawhide XEmacs RPM, I noticed that
Ville> they had tried to use --pkgdir (and failed). AFAICT, that's not used,
Ville> and can be safely removed since lispdir gets set to the same value in
Ville> configure and thus it's mkdir'd anyway in Makefile (mkdir). I'll
Ville> patch against 21.5 and 21.4 if this is correct.
Any comments on this?
Ville> Another thing that needs clarification is --package-path.
Ville> configure.usage says:
Ville> ... PATH splits into three parts separated by double colons (::)...
Ville> AFAICT, the splitting is done in src/fns.c (split_external_path), and it
Ville> uses SEPCHAR for splitting. I suspect configure.usage needs tweaking;
Ville> if I'm right, on Unix (maybe Cygwin) the path is split on *single*
Ville> colons and on Windows, semicolons.
The splitting is not done in src/fns.c, it's done in
paths-decode-directory-path' which sits in in lisp/find-pathse.el.
You've also omitted context which would make this comprehensible.
Specifically, a "part" is not a directory:
--package-path=PATH Directories to search for packages to dump with xemacs.
PATH splits into three parts separated by double
colons (::), an early, a late, and a last part,
corresponding to their position in the various
system paths: The early part is always first,
the late part somewhere in the middle, and the
last part at the very back.
(Each part is then split into directories, and the whole shebang is
then spliced together with other stuff.)
You are correct that it uses `path-separator,', not hard-wired :
splitting the path.
I'm happy to take suggestions on how to improve the wording.
It seems I got confused tracking where the value of the given
package-path is split into "parts", ie. the split on '::', and whether
it really uses '::' on all platforms. If it does, the docs are ok.
scop at xemacs.org