On Fri, 2005-12-30 at 11:30 -0800, Curtis Poe wrote: > We're hoping to avoid bundling Apache2 because that would contradict > the design goal. Specifically, if someone has an existing mod_perl 1, > mod_perl 2, FastCGI or other server, we'd like things to, as much as > possible, "play nicely" with them.
You probably are aware of this, but the difficulty with that approach is that many people run really bizarre apache/mod_perl installs. They compile in flaky modules, or mis-configure things so that your conf additions don't work, or run out-of-date versions with known problems. Trying to cooperate with all of that will put you in the position of remotely troubleshooting every user's local apache problems. > Bundling a bunch of stuff they > don't need would be disastrous. The apache source is pretty small by modern standards, and easy to relocate to a special location where it can be removed simply. > Trying to maintain separate bundles > for every configuration option and OS would also be very difficult. > (different platforms, servers and data stores) Apache/mod_perl builds with the included scripts with no intervention on most platforms. What you're trying to do (add some stuff to the config) should be no problem, but if you run into many issues with people's local builds of apache, I think you may want to reconsider bundling it and building a sane binary during your install. You could always offer both options, to keep the more savvy users happy. - Perrin
