At 09:34 16/10/98 -0400, Greg Klanderman wrote:
What if I'm just Joe User installing packages in
~/.xemacs/packages
and *can't* write to /usr/local/...../lisp/package-get-custom.el?
Well it only needs to be written if package-get-base has changed and it
assumes if you can write packages-get-base then you can write
package-get-custom.
Also, that code is really irritating because it causes my cvs updates
to always fail on that file. So I'm for taking it out of the
distribution, like package-get-base.el.
Suits me.
Maybe then it never actually
needs to get written out, just eval the right forms which you generate
as package-get-base is read in?
I think this would be ok. I don't know how the interaction with custom
would be affected.
Another issue is keeping in sync with package-get-base, which is more
dynamic now. It isn't loaded until you call a package-get function,
and can be updated from mail/news/update files during a session.
Guess package-get-custom should just be updated at the same time.
In the function package-get-update-base-entry should work.
Yes. Again I don't understand custom well enough to understand the
implications of complete run-time updates, but you would have thought it
would be ok. I guess what you don't want is package-get-custom gettting
generated every time you run customize. But I guess the requires could be
dynamic as well.
I'll think about it a little more.
Thanks
andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp(a)parallax.co.uk web:
www.parallax.co.uk/~andyp