>>>> Martin Buchholz writes:
>>>> "AJ" == Andreas Jaeger <aj(a)suse.de>
writes:
AJ> I've uploaded edit-utils 1.44 to
AJ>
ftp.xemacs.org/pub/xemacs/beta/incoming.
AJ> The file bookmarks was not usable with XEmacs 21.1.x, I've applied a
AJ> quick fix from Adrian. I'd like to see a real fix soon.
mb> The current situation with our stable/unstable branches is
mb> problematic. XEmacs 21.1 itself may be stable, but the packages used
mb> with it are in flux. As a result, nobody is even able to reproduce an
mb> install of earlier releases of 21.1, because the packages have
mb> changed.
mb> It might be considered a matter of philosophy whether the packages are
mb> separate from the XEmacs `kernel'. This is similar to the situation
mb> with the Linux kernel. My feeling is that the users don't care about
mb> this distinction, and would like a stable XEmacs and a development
mb> XEmacs.
mb> Unfortunately, the development XEmacs keeps making random changes to
mb> the packages, which break the stable XEmacs. This is especially easy
mb> to do, since the developers typically never run 21.1, and so might
mb> write to a new API.
mb> If we're serious about having a stable and unstable XEmacs series,
mb> that needs to extend to the packages as well.
I fear a maintenance nightmare. I would prefer to have packages that
work with all versions of XEmacs.
mb> In particular, this is a strong argument in favor of at moving at
mb> least the core packages currently maintained by the XEmacs development
mb> team back into the XEmacs tree, or some other measure to ensure true
mb> stability of future stable releases.
But adding packages like xemacs-base and mule-base back to the core
would get my vote.
Andreas
--
Andreas Jaeger
SuSE Labs aj(a)suse.de
private aj(a)arthur.rhein-neckar.de