On Tue, Apr 09, 2002 at 01:37:43PM -0400, Jim Jagielski wrote: > Except if libtool is overkill for what we need. Sure, I'm willing > to continue to try to "work" with the libtool developers, and hope > that we can come to a good working relationship. In the meantime, > I don't see the harm is doing a good review of what we are using > libtool for (is it just figuring out how to handle shared libs/DSOs?) > just in case... as mentioned, I'm sure there's not a consensus on > why exactly we're using libtool.
On the contrary, I think Apache is one of the best use cases for libtool. How many other software projects aim for such wide portability as Apache? The mere fact that we have come across unsupported features and unknown platforms means that Apache's requirements are wider than libtool's features. In my mind that simply means that libtool needs to catch up, not thrown away. And I completely agree with you that we should do a good review of why we are using libtool, but why stop at libtool? If anything I think the fruit of these reviews would be a good FAQ for new developers. -aaron
