Sorry to be chiming in so late here.
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>>>>> "Ben" == Ben Wing
<ben(a)xemacs.org> writes:
Ben> so it does set ~/.xemacs. what should it do instead?
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.
Yes. The problem is that I dropped the ball on finishing to propagate
the changes I made in December 2004.
The thing to do is to propagate the {early,late,last} package
directories separately from configure to the running XEmacs. Could
you guys give me a week to do that, or at least let me review patches
on this issue before they're committed? (I promise I'll be more
responsive than in the past few weeks.)
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla