3. install/copy step needs to bypass the final install location and
copy to some other root
I'd say "should be able to" instead of "needs to", but yep, this would be very helpful.
8. finally, something should be done to rationalize the build of
modules included with aolserver and other modules -- right now
included modules benefit from source-directory build support, other
modules less so.
This would be great. As I said in my response to Dossy, something that makes it easy for modules to build against an interim AOLserver build directory while still being configured to run in a different final location would be very useful, since in many ways it's the modules that make packaging AOLserver 4 difficult, not the server itself.
And, sounds like folks are leaning toward the -rpath stuff being
mostly-good instead of mostly-bad?
IMO, the way this should be handled is to make it available but not mandatory...as just one example, you could have a --runtime-rpath option for the configure script, but have no default -rpath. An approach along those lines is flexible enough to accomodate everyone's needs.
More generally, I'd say that flexibility should be the guiding principle in the build system (goal 0 on your list). The build system should provide as much flexibility as possible to the user and impose as few restrictions as possible, so that users can easily adapt it to many different environments. That's part of why I was citing the build methodologies for things like Apache, BIND, and OpenSSL; they're all converging on a more or less universal way of doing things, and it would be good if AOLserver 4 followed that model as well, since it makes it simpler for people coming fresh to AOLserver to grok how it's built.
- John
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
