Perrin Harkins wrote: > I hear you, but I think anyone who is building a serious web app is > better off compiling the important parts (apache, perl, mod_perl) > themselves. The options that the packagers choose are intended to > meet the needs of the largest cross-section of users, not to work > well for you. They also tend to lag way behind, which is a serious > problem for mod_perl 2 since it has gone through important changes in > the last few months.
Thank you for your reply. :-) My goal is to be able to write Apache2/ mod_perl2/ MySQL applications and then sell and/or give them away with the instructions "it works under *nix distribution X version Y.Z with packages A, B, C installed". If people want to customize their box to improve performance, that's their choice/risk. I need a stationary target to develop and release against. One of the problems I'm facing right now is that my web hosting provider uses an internally-customized *nix distribution with Apache2/ mod_perl2/ MySQL. I've been trying to match it using Debian 3.1, and it's been a losing battle. Furthermore, the hosting provider makes changes to their environment according to their needs and wants, and I find out the hard way. This is an untenable situation. The solution is to apply configuration management, change to VPH hosting, and use the same *nix distribution everywhere (development, test, production). Any other suggestions/ comments/ recommendations? David
