> They're dirty unix hacks, that's why! :)
I don't think they are hacks, but I will agree they are somewhat hard to
use.
However, I did manage to learn enough to get JServ building just fine and
there is a huge collection of useful code in JServ that could easily be
migrated over to Tomcat if someone wants to take the time to do it.
> And because if you use
> autoconf/automake under unix, you will loose the ability to have
> parallel builds on another operating system wich doesn't support those
> (ala Windows or MacOS/X)...
Uh Pier, this isn't true at all.
auto* works just fine on MacOSX.
As for Windows, ppl can install cygwin and autoconf/automake work just
fine there as well. I even compiled and installed wget on my Win98 box
under cygwin with gcc/autoconf/automake/etc without any problems.
> And also there's a slight problem with licensing... AutoConf and
> AutoMake are GPL... I am not 100% convinced that we can include them as
> a part of our distribution...
Another thing that isn't true. There is absolutely no issue with
licensing. In fact, Apache 2.0 is built using autoconf.
I think that people who compile things in C are used to using configure
and I think that we should support it. But, I'm not willing to do the work
so I guess whatever everyone else wants to do is fine with me.
I will say though that I don't approve of giving people bogus reasons for
the reason that we are not currently using it. I think the end reason is
that if someone wants to see it used badly enough, then they should take
the time to contribute the code to use it.
Sorry to disagree with you Pier. :-)
thanks,
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
