> Ok, let me state that a bit better... why do we check for Netscape, > which seems to pass on my system (which has no Netscape) and then do nothing > with it?
Because what looked like a good idea at the time later seemed to be bogus to me. I think we could remove netscape4-plucker-helper.in, and the associated check for netscape. > The other thing I notice, is that our checks for --disable-foo are > ignored, and things like the gtkviewer, etc. are attempted to be built > anyway. I'll plod through it later this week and see if I can iron out some > of the wrinkles there. I've picked up more about autoconf in the last 6 > months that I probably ever wanted to know.. ;) I actually have a number of patches to configure.in to fix this that I'd like to check in. But it's a policy thing. I think the configure scripts should, if invoked with no command-line switches, check for the presence of various tools, and only attempt to configure/build those parts of Plucker for which the tools are available. What the current configuration script does, however, is crash if some tools are not available. I've fixed this, but it does make configure work a bit differently; everything is implicitly disabled unless the tools are available for it. What do you think? Bill _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
