Martin Buchholz writes:
[...]
With the current package model, there is _no_ _way_ for any user to
get a stable version of XEmacs. This is a quality control disaster.
Maybe. It's true if you believe that all that code is our
responsibility. One point of breaking out the packages is that
we no longer are responsible for the quality of all the code
that claims to run under XEmacs. The stuff distributed ouside
the core XEmacs is not part of XEmacs anymore. Your statement
is false if you believe in the new reality, as I do.
I'm serious. We need to stop thining of every piece of Lisp in
the package tree as being part of XEmacs and our responsibility.
Today's model more clearly reflects reality. We could put all
the code back into the distribution and pretend that we were
doing quality control. But that doesn't mean QC will actually
get done. Past evidence indicates that it won't, which is part
of what drove us to push the ever increasing pile of Lisp code
out of the distribution.
Getting a stable XEmacs is the same as getting a stable working
environment involving an operating system and some number of
applications. Unless you get the whole bundle from a vendor,
there will be some experimentation involved in getting a setup
you're satisfied with.
[...]
The packagizing of XEmacs has been bad for XEmacs. With a lot of
work, it could be a good thing. Who will do that work?
Well, that's certainly provocating enough to get discussion
going. :)
My opinion: the XEmacs audience is largely computer professionals
who will have no problem using 'tar' (or similar) and installing
the packages they need to get work done. So I think providing a
fancy interface over the package system is largely a waste of
time. We need a way to keep unstable packages from the stable
ones, so the user gets a choice. We need a way for the user to
easily see what they need to install to get a certain feature.