> Yeah; this whole thread is premised on working around the
> problem without an Apache software change. It's a reasonable
> premise (IMO) -- if you've got a custom compilation and a lot
> of modules, that can end up being a lot of software. I build
> a PHP4+SSL+Apache+IMAP+etc. source tree at one point, and it
> ended up being ~1.2 million lines of code, all told, that had
> to be made to work together. If you had "just built it", then
> it would be very hard to update just one component without
> repeating the whole process. My advice? Use CVS.
Actually, this whole thread is premised on I have a dev system with 16
jailed apaches and it would be a pain to upgrade all 16 of them vs. just
making one global kernel/environment change. It sounds like that is
probably a pipe dream though..
--PT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
