>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch&gt; writes: Jan> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> I'm much more concerned with Ben's wish to recognize xemacs-packages >> alongside the source tree. Jan> I still don't understand this. I have had my packages in the source Jan> tree for ages and that works (the only that doesn't is that the srcdir Jan> builds does not make the proper links yet like it does for lisp and etc). What Ben wants is to have the package hierarchies *outside* the source tree like this: xemacs-21.2/ (source tree) xemacs-packages/ (package hierarchy) The problem is that the CVS module is *also* called xemacs-packages, but a checked-out package tree is not a package hierarchy. So if you have this layout: xemacs-21.2/ (source tree) xemacs-packages/ (package tree from CVS) (as I do) things won't work right: you then need an xemacs-packages directory with a real package hierarchy underneath xemacs-21.2. Note that all this is *only* for running in-place. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla