"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
But I see these issues as a bug in CVS. Current XEmacs development
is
more a forest than a tree. We don't really _have_ a mainline at this
point, except by administrative fiat and historical accident. Besides
21.2, there is 21.2/Mule/NT, 21.2/UTF-2000, and soon 21.2/gtk-xemacs.
Some of these features will probably merge soon, others not.
Is there a reason for all of these not being configurable by
--with-gtk or similar?
Right now I have xemacs-21.1, xemacs-21.2 and gtk-xemacs checked out,
and I'd like to test UTF support.... creating different branches for
every projects is a nightmare in CVS.
IMHO, giving someone a branch to work on creates more problem in the
long-run than making all development take place on HEAD, hidden by
--with-foo (defaulting to off) switches for experimental stuff. A
project replacing, say, the garbage collector, inside a branch might
make it hard to integrate it with HEAD in the future. If done in HEAD
from start with a configure switch, it would only require flipping the
default value once it's ready.
Also, it's easier for users to test things if they only need to say
--with-foo rather than setup a separate build environment. And users
are everything, aren't they? :-)
(Yes, of course it's a bug in CVS, but I don't believe it will be
fixed soonish.)