Re: One more time, why can't xemacs-packages be a sibling of xemacs?

dv> Obviously, XEmacs took my package source directory for what it dv> is not. After renaming it to XEmacs-Packages (note the dv> uppercase) and reinstalling in order to update the symlinks, dv> everything went fine again. ms> Ben yelled at me sufficiently to implement this. It's an ms> intentional feature, and it only happens with an in-place ms> XEmacs. Stephen> This, er, doesn't seem to be documented anywhere. info xemacs Stephen> 'startup paths' says "If you run in-place, these [hierarchies] are Stephen> direct subdirectories of the build directory." Correct, I haven't gotten around to that, mainly because I expected there'd be dust in its wake that would need settling. The proof is here. Stephen> What is it that Ben wanted? Actually, I am not sure anymore. Stephen> Is this just so that Windows users can put their installed package Stephen> hierarchy in c:\xemacs-packages and their sources in Stephen> c:\xemacs or something like that? That's how I read him originally. dv> To me, running in place would mean the ability to find the dv> packages in my compiled cvs source tree withtout having to dv> install them (whether by symlinks or not). But that's not that dv> hey ? You're correct. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla