Jake> But as far as packages go, I can only have one copy. This should also be configurable using --package-path=$PATH Do NOT insert any doubled colons, see ./configure --usage for more information about --package-path. I'm sorry I don't know what "early", "late", and "last" packages are supposed to be (see the usage message), or how they get defaulted.... But the above form should be safe. Jake> Should I be using the beta packages if I want to test the Jake> beta or go with the standard packages? If I choose not to Jake> install and instead run it out of the soure tree, as Martin Jake> suggested, could I then associate the beta packages somehow Jake> with the beta xemacs? At the moment, there really isn't any such thing as "beta" packages. That's the point of separating core development from package development. (There are beta Lisp libraries, but these are closely bound to the C code and live in .../lisp/ in the XEmacs source tree and in the version-specific .../lib/xemacs-$version/ hierarchy, not in the package hierarchy.) If you want to participate in beta package development, you should get the CVS tree for the relevant packages, and participate in upstream discussions. The "bug" in the organization is that some packages are maintained by XEmacs developers, and they sometimes use beta features without testing for them. These packages then break on the stable release. So using the most recent packages with the stable XEmacs actaully helps alot by chasing thse bugs out into the open. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."