Re: 'package' directory location?

Vladimir> Where is the standard (i.e. most natural) location for Vladimir> the CVS 'package' directory relative to the CVS Vladimir> 'xemacs-21.5' directory? There is none; I always put them side by side. The XEmacs executable doesn't care where the package sources are, only the installed packages. Since the packages currently cannot be used "in-place", you have to install them somewhere. (We have a kludge that installs symlinks rather than copies to save space, but this is not part of the source tree.) Mike Sperber has remarked that the "natural" place to install bleeding edge packages is xemacs-21.5/{xemacs,mule,site}-packages, and a run-in-place xemacs binary (ie, in xemacs-21.5/src/xemacs) will find them there automatically. I think this is unclean, and prefer to install my packages (eg to /usr/local/lib/xemacs/{xemacs,mule,site}-packages), using the configure option --package-path='~/.xemacs::/usr/local/lib/xemacs' to build XEmacs. Note: site-packages are for local packages; site-lisp is deprecated, and reasonable places to put local lisp libraries is in site-packages/lisp/local, relative to one of the package hierarchy roots in --package-path. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py