A friend who works at an ISP was really annoyed by this "attempt to
prevent everyone trying to use those release". He pointed out
basically that PHP is the dog and PEAR is the tail, and thus it is
the job of PEAR modules to work around PHP bugs, not to create
inconveniences or impossible situations for users. And that security
updates are first priority above all else. Oh, and he said all this
amidst a dazzling barrage of profanity, which I've filtered out ;-)
Sounds like he's too used to Microcrap software where they expect you to use up all your effort working around their bugs, rather than working with the parties involved to solve the issues.. (which was done within hours of the release going live.)
He also suggested that automated regression testing might be helpful.
That seems reasonable to me too.
I think that has been added to php4's test suite now.
As was pointed out, the real blame lies in the people who didn't test 4.3.10 RC releases - me included ;)
Regards
Alan
Anyway, it works and I think I understand now what's going on. Thanks
for explaining.
- -ken - -- - --------------- The world's most affordable web
hosting. http://www.nearlyfreespeech.net -----BEGIN PGP
SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBz5ofe8HF+6xeOIcRAloyAKCw7c55ZcO1p+4CPO9YPoK63OZGiACfUKDO DFR/4q26Jiuc44nu/71yPVk= =ZQht -----END PGP SIGNATURE-----