>>>> "Malcolm" == Malcolm Purvis
<malcolmp(a)xemacs.org> writes:
>>>> "Ben" == Ben Wing <ben(a)666.com>
writes:
Ben> Until someone checks in configure.ac, it's *their*
Ben> responsibility, imo, to keep up with patches to configure.in.
Malcolm> I agree :-)
Well, that's up to you. But I disagree when it comes to new features.
I would really prefer you help Ben port his features forward to
configure.ac now, and abandon the work on configure.in---leave that as
a fallback in case either you or Ben hosed configure.ac. And it's not
just your effort/needs: I've already put in several hours on
configure.ac (and regressiontest.pl), and Steve Youngs would like a
robust version asap, too.
Malcolm> Until then I have no problem with people making changes
Malcolm> to configure.in.
I do, though, because I will be checking in your changes plus my own
to the sjt-xft branch as soon as I find time to do it---I have some
experimental autocrap of my own to support Xft development that I
would be unwilling to commit to the mainline.
Malcolm> BTW, Stephen's comments about SuSe mean that I should
Malcolm> look into doing a 21.4 version as well so that we can
Malcolm> make their release schedule?
No. SuSE has their patch for 21.4. The issue for them is purely
political, to make it look like we're doing the kinds of things we
need to do to make 21.5 a product they can support.
You're certainly welcome to do an SXEmacs version, but I see no gain
and lots of pain from applying to 21.4. But if I were Steve Y, I'd
just stick that thing in there and see what breaks. I bet on "not
much, and that very obvious to diagnose and fix".
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.