Jan Vroonhof writes: One objection I have to the package system is the idea that the "main XEmacs releases" (which I will call "XEmacs distributions") are the core and only the core. Instead of trying to figure out what should be in the core and what shouldn't (and failing terribly in the case of xpm-button-create), a better solution would be to make an XEmacs distribution the core and some set of bundled packages. The set of bundled packages should at least be enough to bootstrap XEmacs to use the PUI to download the remainder of the packages from the web/ftp sites. Right now, this means xemacs-base and efs; whenever the http-based package system that I've heard mention gets written, it can replace efs. At the other extreme, the bundled packages could be contents of the sumo tarball. In practice, you'd probably go for the something in the middle, say the most "popular" packages. This still gives you the flexibility of releasing packages on a different cycle than the core, but gives you more than a barely functioning XEmacs. -Mark