Richard writes:
it would be very convenient if there were always a very up to date
sumo
tarball on the server, or maybe I have missed that?
No, it wouldn't. Packages with major changes need to shake down
before being installed in the SUMO. This is like upgrading your OS;
you will get a few bug fixes that are critical to you, but you will
also get a raft of new bugs and incompatibilities. The SUMO should
change realtively slowly, and users should use individual packages to
upgrade their mission critical functionality. I don't care if they
use M-x list-packages or if the use RPM, of course.
And while builtin package management is nice the current state of
things makes it unnecessary hard to build packages installable by
distro tools such as rpm and apt.
In what way? I gave up on trying to manage my local builds with dpkg
long ago (no benefits), but when I did try it, it wasn't hard at all.
Just a little tedious if I tried to do it on a per-package level. For
distributed packages, it was even easier: a generic debian/rules to
fetch the package from
xemacs.org as usual, untar it somewhere, and
let dpkg tar it back up and move it into place. (But that violates
Debian guidelines about building packages from source.)
A sumo tarball that is intended to work with a particular xemacs
release would help a lot.
I don't understand. All SUMOs are explicitly intended to work with
each particular XEmacs release.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta