Ville> Hmm, while looking at the newest RH Rawhide XEmacs RPM, I Ville> noticed that they had tried to use --pkgdir (and failed). I don't know about that. Ask Mike Sperber [Mr. Pathfinder]. Ville> Another thing that needs clarification is Ville> --package-path. configure.usage says: configure.usage is 100% correct on Unix and Cygwin, and since Windows rarely is a true multiuser system, I think we should wait for the FAQs rather than pointlessly bulk up configure.usage. The three parts of the --package-path argument have rather different semantics, and each part can be an ordinary search path. Thus the doubled colon. The semantics only make sense when an admin might be installing for multiple users, each of whom might have their own package installations, and (optionally) there's a legacy 20.4 package tree installed. So normally it's an ordinary colon-separated path. -- Institute of Policy and Planning Sciences 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.

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 send a Ville> patch against 21.5 and 21.4 if this is correct. 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 : for splitting the path. I'm happy to take suggestions on how to improve the wording. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

Ville> On Fri, 2003-01-03 at 11:22, Michael Sperber [Mr. Preprocessor] wrote: >> >> 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 send a Ville> patch against 21.5 and 21.4 if this is correct. Ville> Any comments on this? Well, --pkgdir is purely historical, and thus, any use of it in modern-day incarnations is probably a mistake. Ville> It seems I got confused tracking where the value of the given Ville> package-path is split into "parts", ie. the split on '::', and whether Ville> it really uses '::' on all platforms. If it does, the docs are ok. It probably doesn't. But somebody else argued that it's better to leave that part alone. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla