[ I forgot to cc: the xemacs-beta list. ] Ben Wing <ben(a)666.com&gt; wrote: In addition to having some installer install a binary XEmacs, what about add-on packages? While it would be nice to select packages to install at install time, what about adding packages after installation (or upgrading existing ones)? Having to go back to the installation program to install packages isn't friendly, and it doesn't address upgrades. What if we modified package-get.el to optionally look on a local disk before trying to download a remote file? If this is done, PC users could have a CDROM with all of the packages on it. We wouldn't even have to change the distribution format (e.g., .tar.gz files), as there are some freely available PC programs that understand .tar.gz files. [ For example, I've got a WIN32 version of djgpp's djtar (it's compiled with MS VC++, not djgpp) which extracts .tar.gz just fine. ] Of course, we'd need subprocesses to work in NT XEmacs. ;-( -- Darryl Okahata Internet: darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.