Re: [Q] Re: [PATCH] all my package fixes, mostly build-related

Ville> I have this setup ("default staging" means the place where Ville> "make install" dumps the packages by default): Stephen> ~/cvs/xemacs/packages (contains the packages working dir) Stephen> ~/cvs/xemacs/xemacs-packages (default staging for non-mule packages) Stephen> ~/cvs/xemacs/mule-packages (default staging for mule packages) Ville> ...and then symlinks: Stephen> ~/.xemacs/xemacs-packages -> ~/cvs/xemacs/xemacs-packages Stephen> ~/.xemacs/mule-packages -> ~/cvs/xemacs/mule-packages Stephen> This is more or less what Michael recommends. (He actually has them Stephen> in the build root for the core.) It is not something that we can or Stephen> should enforce, IMHO. Ah, no, I've never recommended that. I've advocated symlinks in the build directory for running *in place*. You can also run side-by-side, but it's something I'm less and less happy with. Ville> Anyway, the point is that it looks to me that one doesn't Ville> *have* to use --package-path for the "personal Ville> installation" case. --package-path is almost always a bad idea, because it disables crucial parts of the XEmacs logic for constructing the package path. Given that the package path is a complex beast, this is asking for trouble. Stephen> Of course. The problem is that if (like me, mostly) you have a Stephen> site-wide installation of the packages and a personal installation of Stephen> XEmacs, 21.5 doesn't work out of the box, while 21.4 does. Could you (re-)describe what precisely you're asking for. I'm thoroughly confused. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla