On Friday 12 September 2003 08:06 pm, Steve Phillips wrote: > At 18:25 12/09/2003 -0400, you wrote: > > If PHP were to release their software in RPM format as some other vendors > (MySQL etc) do then you would be able to use this to upgrade or replace > your PHP RPM.
I am have not built any RPM at all, but I think not all software can be easily made an RPM. PHP is one example. It has many many configure options. For example, it has different configure options to support for different database: MySQL, PostgreSQL, Oracle, OCI8, also graphic library, PDF, all kind of stuff. How do you suppose to make an RPM? Compiled with all that? you get a big bloated version of PHP will stuffs you don't need. Then also for db supports, it depends on the client library of the databse. There is no way whoever compiles PHP for RPM at php.net knows where your database is going to be, or what version, etc. Redhat can do it because they also the one who compiles and provide MySQL RPM, PostgreSQL RPM, for example, that's why there is dependencies, and you can't usually just upgrade php-mysql*.rpm version without upgrading mysql-client*.rpm version, and php-*.rpm version. But if you require PHP people to do it, then do they have to provide the corresponding mysql also? If not, then you run into dependency hell. <snip> > > By installing a compiled version of PHP over the top of an RPM without > removing the RPM first or compiling with the same or similar options as the > RPM was compiled with is asking for trouble. Not necesarilly. You can compile and install PHP at different place, et /usr/local/php-4.3.3, and then just change httpd.conf and make sure you link it to the correct place. There is no reason why this is asking for trouble. You can even have different versions of php installed on one machine, if you just make sure you run the correct binary that you want on your path. Done that. > It appears you have only a few > options left to you. Either adapt your code to suit the older PHP version > (probably the easiest way out) or un install all the RPMS to do with > PHP/Apache, download the PHP/Apache/other needed packages and then > recompile the lot - that way you can be sure of having an untainted build. Don't need to uninstall apache. Just make sure it's loading the correct php module should work. > If the box has to go live by Monday then it is unlikely you will find any > other answer if you get stuck from the list by Monday as it has taken > almost a week to get this far, in this case - if the dates can not be > pushed back - I would suggest looking into re-writing your code around PHP > 4.2.2, at least that way you _know_ it will work. I would say it's much much easier to recompile PHP than adapting codes, especially if it's complex codes. I am a PHP developer myself, and as I said earlier, it does not take that long to recompile php. RDB -- Reuben D. Budiardja Department of Physics and Astronomy The University of Tennessee, Knoxville, TN ------------------------------------------------- /"\ ASCII Ribbon Campaign against HTML \ / email and proprietary format X attachments. / \ ------------------------------------------------- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
