On Wednesday 04 August 2004 08:09, Eugene Lee wrote:
On Tue, Aug 03, 2004 at 05:27:45PM -0400, Michael W Cocke wrote: : The PHP crew isn't content to just add new features - my complaint is : that they think 'backward compatability' happens to someone else. I'm : not kidding - I rewrote the same application (a fairly complex one) : three seperate times - every time I upgraded php 4.x, I had to go : debug the whole app again! : : I'll never touch a PHP app again, unless someone else writes it, and I : won't upgrade my php unless it's at gunpoint and someone else has : already tested the app against the php version.
Not SuSE related, but what coding practices did you follow that caused you so many headaches and rewrites through the php-4.x upgrades (and including the newly released php-5.x)?
I have setup a new system! Old applications are not the case for me. However, when I am already on a new system, than I could go the extra mile for the newer version, of course only if it is stabled and has advantages. Is there a rpm or any installation help or do I just download from php web site the stuff and compile it by myself. That brings me to the question, when I do something outside of YAST, I loose all the advantage of YAST. How can I do that smoothly. E.g., I have upgraded the kernel to 2.6.5, now everytime I open YAST it wants to "upgrade" to 2.4.x!!! Once I accidently said yes to it, .... and was back at 2.4.x. Is there a way to say permanently NO to a "downgrade" ??? bye Ronald