Futures and some Packaging issues I've been working on

In the last couple of days I've been working on: 1. (Re)Building Lisp packages from scratch. Building non-Mule Lisp packages will be supported in the next package update. This is tested and working. 2. A procedure for building both a new XEmacs and new Lisp packages checked out from source from cvs.xemacs.org. This is tough, and probably won't be supported until after 21.0 release, and only on Unix with a heavy installation of GNU tools until someone gets around to porting it to Cygwin. The more I think about it, the less I like anything extra(==external) dumped with XEmacs, Hrvoje's objections notwithstanding. Can we merge the mule-base package back into the core without too much bitching if there is a way to jettison it if XEmacs/Mule isn't desired and it is distributed as xemacs-mule-XX.X-bYY-mule.tar.gz?