Re: with-package-prefix

Ben> so it does set ~/.xemacs. what should it do instead? After some discussion with Mike, it seemed simplest if ~/.xemacs has the same structure as /usr/local/lib/xemacs: it should have xemacs-packages and mule-packages (if the user has mule-specific local packages but uses no-mule XEmacsen, otherwise mule-packages is not needed). Probably the code should do if test -z $package_path -a -n $package_prefix; then package_path=~/.xemacs/site-packages package_path=$package_path:~/.xemacs/mule-packages package_path=$package_path:~/.xemacs/xemacs-packages package_path=$package_path::$package_prefix/site-packages package_path=$package_path:$package_prefix/mule-packages package_path=$package_path:$package_prefix/xemacs-packages fi Ben> btw probably it should also take multiple prefixes; i'll see Ben> about fixing this. Please don't mess with this. Fix the default, yes, if you agree that the above default is acceptable. However, there's no apparent demand for multiple prefixes. What everybody who's posted wants is to set _one_ system prefix, and for configure to set up defaults for user packages so XEmacs automatically picks them up. Also, I haven't worked out the configure UI for packages-in-source-tarball yet, and multiple prefixes will make it more complex to adapt to existing installations. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.