"manually" updating PHP on Suse 9.1 (to PHP 4.3.10)
I've got one or two questions egarding those still missing critical PHP updates. Suse 9.1, Apache2, mod_php 1. AFAIS, in Suse 9.1, most modules can be found in /usr/lib/php/extensions. Would it be sufficient to download PHP 4.3.10 from php.net, compile and install it into a different directory (--prefix), to get rid of the bugs? AFAIS, (un)serialize() and (un)pack() are part of the PHP core. 2. To "get back" to SuSe RPMs, is it sufficient to install the Suse apache2-mod_php-4 RPM as soon as it is available? (And perhaps to manually remove the install directoty from step 1 above). The RPM should overwrite /usr/lib/apache2-prefork/libphp4.so and all other newly installed files, I presume? Thanks for all comments - even if those questions *are* a little dumb, I fear. :) -thh
Thomas Hochstein schrieb:
I've got one or two questions egarding those still missing critical PHP updates.
Suse 9.1, Apache2, mod_php
1. AFAIS, in Suse 9.1, most modules can be found in /usr/lib/php/extensions. Would it be sufficient to download PHP 4.3.10 from php.net, compile and install it into a different directory (--prefix), to get rid of the bugs? AFAIS, (un)serialize() and (un)pack() are part of the PHP core.
2. To "get back" to SuSe RPMs, is it sufficient to install the Suse apache2-mod_php-4 RPM as soon as it is available? (And perhaps to manually remove the install directoty from step 1 above). The RPM should overwrite /usr/lib/apache2-prefork/libphp4.so and all other newly installed files, I presume?
Thanks for all comments - even if those questions *are* a little dumb, I fear. :)
Have you had a look at ftp://ftp.suse.com/pub/projects/apache/php4/9.1-i386 the changes:
------------------------------------------------------------------- Thu Dec 16 21:39:30 CET 2004 - poeml@suse.de
- update to 4.3.10
------------------------------------------------------------------- Fri Sep 24 14:36:03 CEST 2004 - poeml@suse.de
- update to 4.3.9 - reverted dlopen flag back to RTLD_GLOBAL (bugs #39197 and #41866), php4-recode now conflicts with php4-imap, php4-mysql and apache2-mod_auth_mysql, mod_php4-core does not require php4-recode any more
Regards Christian
Thomas Hochstein wrote:
1. AFAIS, in Suse 9.1, most modules can be found in /usr/lib/php/extensions. Would it be sufficient to download PHP 4.3.10 from php.net, compile and install it into a different directory (--prefix), to get rid of the bugs? AFAIS, (un)serialize() and (un)pack() are part of the PHP core. Do you still need the PHP come with SuSE 9.1 ? If no, then you can uninstall it and install the PHP from php.net.
The default location for PHP from php.net is /usr/local (but of course you can change that). So it will not overwrite the SuSE PHP modules.
2. To "get back" to SuSe RPMs, is it sufficient to install the Suse apache2-mod_php-4 RPM as soon as it is available? You better use YaST for this.
(And perhaps to manually remove the install directoty from step 1 above). You cannot remove PHP installed from tarball using rpm.
-- Tedi Heriyanto URL : www.tedi-h.com GPG fingerprint = C02C 7797 0EF0 5D25 798A 0A25 1DD3 6924 57C7 5D78
(And perhaps to manually remove the install directoty from step 1 above).
You cannot remove PHP installed from tarball using rpm.
Thats right, but if you run checkinstall instead of make install, you'll get a rpm. http://checkinstall.izto.org/ also included in suse.
participants (4)
-
Christian Hernmarck -
Kai Hauser -
Tedi Heriyanto -
Thomas Hochstein