I have also been thinking about adding the ability for a package to
specify a Lisp form to evaluate to indicate
whether it should be loaded. This way, we can do things like move
packages into the core, provide different versions of packages for
different XEmacs releases or +/-mule, make a separate mule-packages become
unnecessary, etc. Makes it much easier to have a unified set of packages
without crimping our style.
This is actually really easy to implement, and does not require any major
overhauling. Someone want to do it? If not, I'll do it when there's
time.
ben
Jan Vroonhof wrote:
Kyle Jones <kyle_jones(a)wonderworks.com> writes:
> Where are we as far as nailing things down for a 21.2 release?
> Stabilizing your widget stuff was one of the pre-release
> objectives. What else?
- Actually making use of any of the widget stuff beyond the tabs?
- Ironing out the remaining kinks in the new menu structure.
- The dumper support.
- Package support fixes
(i.e. starting from allowing a xemacs-<version>-all.tar.gz file upto
finding a solution to replace News). I am supposing it is too late to
actually implement a great overhaul of the package code that was
discussed a few moons ago.
I wanted to complete the custom themes stuff, but in its current state
it can lie dormant if we wish. So it won't delay any release if I do
not find the time.
I think we should also release a few betas with clash-detection
enabled to have it exercised.
Jan
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/typing.html.