At 02:42 AM 5/14/98 -0700, you wrote:
I'm asking what is the minimum amount of code required. The
defcustom
per package code must not be part of the XEmacs core.
>> It doesn't need to be generated at build time, it can be
installed at
>> run-time and have the same effect.
> You mean when someone tries to customize packages?
No. I mean this must be installable independently of the XEmacs
core. That will be the case if it's a package of its own.
I think it should always be auto-generated though - its intimately tied to
package-get-base.el or are you talking about putting package-get-base.el
and package-get.el in a package as well? If package-get-base.el and
package-get.el are in the core (which they are currently and which I like)
then you could just generate package-get-custom.el on the fly when a user
tries to customize packages.
I still am confused though. What process do you envisage a user or builder
going through.
Bang on me in xemacs-beta if this isn't 100% clear.
To address changed. :)
andy