On Tue, 10 Feb 2009, Tom Boutell wrote: > 3. Make it part of your admin's job to follow the PHP new releases > blog and immediately rebuild PHP whenever a new 5.2.x release comes > out. This is the only responsible way to build PHP from source on a > production site. There are RSS feeds here: http://www.php.net/ > > I follow the third approach. I was reluctant to do so because I have > MANY things to do other than system administration and I value the > fact that official OS packages retroactively backport security patches > from newer releases
That does not always happen and eventually you will be forced to upgrade the OS just to get support. > (at least while your distribution is still > supported). But PHP is important enough to me to be worth the > additional time and effort. I am working with certain clients to make > sure they ALSO follow such practices rather than just getting me to > compile PHP 5.2.x as a one-off and then walk away. Which is as bad as > installing an old release of WordPress and then walking away from your > client and saying "oh gee" when they get hacked a year later. (: Option 3 is fine when you have a few machines but eventually I got to option 4: 4) Switch to a source-based OS. -- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
