<blockquote> What I would really like to do is create a standard source tree (or
trees) to build the necessay software to install OpenACS. Once
AOLserver is built to need requirements I think we should freeze
this code and work on creating binaries, OS specific packages, and
a source tree that can easily be installed. I can build just about
any package format expect BSD ports (I've just never had too). I'd
like to add an options conf-dist so that package maintainers can
all pull from the same base.
</blockquote>
Well, that's mightily generous AND impressive, Matt...as long as we don't make that a REQUIREMENT for use of OpenACS. (ie, using AOLServer from "our" tree). Take a Debian linux distribution, for example. Debian already HAS a AOLServer 3.4.2 install, managed by a Debian maintainer, included in the standard distribution. I'd much prefer to be able to use the existing AOLServer package, even if I have to use their source package, and patch it. That make sense? I guess I'm just not clear as to whether or not you're trying to make some conveniences (which are great, as long as they don't preclude the "ordinary" use of OpenACS), or a new way of packaging OpenACS to require the use of "our" version of AOLServer (I wouldn't think that would be a good idea...)
Thoughts?
