If I recall correctly, bootstrapping from package sources is not easy. Unless you plan to develop packages, there's no reason not to go with binary packages. Once you have EFS working, updating them is trivial with pui-list-packages. For package-path, since you want to run in place, just pick a directory somewhere and install the first few binary packages there. You might choose /usr/src/xemacs/xemacs-packages. But don't choose the xemacs source lisp directory as you did below. Then use pui-list-packages to get more packages. And relax. This is beta, after all. Sam> Sam> Sam> Hopeless. I want to get the packages via CVS and keep them under Sam> /usr/src/xemacs/lisp/. They are /usr/src/xemacs/lisp/xemacs-w3/*, Sam> /usr/src/xemacs/lisp/xemacs-gnus/*, &c. I will **NOT** be installing Sam> XEmacs under ${prefix}, so if it cannot be run "in-place" with the Sam> packages I want, just say so and I will leave you alone. Sam> Sam> So, what are the **EXACT** instructions? Sam> Like what should the --package-path argument be? Sam> (I tried `--package-path=/usr/src/xemacs/lisp/' and got compile errors). Sam> What do I type at the terminal? Sam> like Sam> Sam> $ cd /usr/src/xemacs/ Sam> $ ./configure --package-path=/usr/src/xemacs/lisp/ Sam> $ make Sam> $ cd lisp/xemacs-base Sam> $ make Sam> Sam> ???? Sam> Sam> Look folks, I did RTFM, and I have installed numerous programs in the Sam> past. It might sound presumptuous, but I would say that if I can't Sam> figure out the docs, at least part of the problem is with the docs. Sam> Sam> Thanks.