>Maybe if everyone used the RPMs you rolled there wouldn't be >any problems, >but it seems that people want to take one RPM from every site, >throw them >all together, and hope they work. Then they don't because one package >wasn't compiled with the right options (like EAPI) There just >seems to be >too many variables if you want to use RPMs to build Apache/mod_ssl, >especially since a lot of people would also like to use RPMs to install >other Apache modules I'm sure (php, mod_perl). It also seems >that a lot >of the people that come to the list reporting Apache/mod_ssl >crashes are >using RPMs. I have send many RPM (php3, Jserv...) to be used with mod_ssl. Everybidy could find them at http://www.modssl.org/contrib/ just where apache-mod_ssl.rpm lives ;-) >> > Why will your project manager kick you for recompiling >Apache? You'll only >> > be down for a second or two when you install the newly >compiled Apache. >> >> Maintenence? It's easier with RPMs... > >Can't argue with you there. RPM is +1 for maintenance ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
