On 1/17/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
> Well, I unpacked ESS into site-lisp with 21.5 on OS X and it does find
> it. I don't see why 21.4
> on Windows should be different. And, if it was different, then what is
> the purpose of the
> variable inhibit-site-lisp? I think this is a bug. Oh, and I tried the
> site-packages trick
> and it didn't find it; only site-packages/lisp was there. But, now I
> see why that wouldn't work.
> You have the directory site-packages/lisp/fsf-compat. No non-xemacs
> package has a directory
> structure like that. A non-xemacs packages would have
> site-packages/ess/lisp or some-such.
> So we need to either fix site-lisp or make the search in site-packages
> also find site-packages/*/lisp
>
Hi Rodney,
I don't know how to make the native Windows configuration process
respect site-lisp, so I didn't turn on that option when building the
native Windows kit.
I do, however, know that when I run configure --help in 21.4, the
output tells me:
--with-site-lisp (Bool) Search a site-lisp directory in the XEmacs
hierarchy before the packaged Lisp. DEPRECATED.
I'm sure Mike Sperber will have some comments when he sees this
thread. (I also suspect that David Kastrup will agree with you that
'site-packages/*/lisp' should be supported.)
FWIW, I think it's unlikely that the (stable) 21.4 branch will ever
support the new feature 'site-packages/*/lisp', but sometimes patches
convince me to change my mind.
Regards,
Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver