PHP 5.0.0 final release is getting closer. Is it possible to have ebuilds for the rc2 version? The portage tree laks of any 5.0.0 version of mod_php and have only the 5.0.0_beta1 version of php cli. Thanks in advance. Reproducible: Always Steps to Reproduce:
php-bugs: we really need to get to a decision regarding the eclass naming and SLOT issues for php5 first...
tal: for the eclass naming, I'm inclined to go with Stuart's idea of a seperate eclass for php5, given the scope of the changes to the existing eclass. it also gives us a chance to clean it up. call the new eclass 'php5-sapi.eclass' and commit it. is the SLOT problem dealing with how to have mod_php4 and mod_php5 with apache[12]?
Ok, i agree too with the naming scheme. This is indeed the SLOTting problem. One possible solution would be splitting the packages to (mod_)php{4,5}, but i don't really like this...
This slotting problem will be resolved before the 5.0.0 final version of PHP will be out or not? I agree with you that the decision is not simple as it seems but a lot of people are asking for php5 support in Gentoo. Tnx in advance.
Why must mod_php be a seperate ebuild? A cleaner aproach (imho) is to build the modules along witht the cli version if USE="apache2?".
Regarding the slotting issue, upstream PHP folk say you can ONLY have one of mod_php4/mod_php5 with apache at any one time, you cannot have both of them due to symbol conflicts. That said, we can just carry on using the existing slotting mechanism we have for mod_php. john: USE=apache2 has a specific meaning - 'Chooses Apache2 support when a package supports both Apache1 and Apache2'. That said, USE=apache2 is not appropriate for this, and what if I want _different_ versions of the cli and mod_php, or to have them built with different USE flags? We definetly want them to use seperate .ini files as well, so that some items can be turned off for mod_php to make it more secure.
So what can I do to help? I really need this ebuild, all the ones floating around the forums are broken. Could you make an ebuild as clean as php-5.0.0.ebuild for mod_php using the php5-sapi.eclass? Just put what ever you've got in the tree and I'll do some bug testing.
Okay, I've committed a 'first cut' mod_php-5.0.0 ebuild into Portage. It should appear on your local rsync mirror in about an hour. I'm pretty sure that this ebuild will need some improvements before it's up to the same quality as Robin's PHP4 work. Please, test it, and let us have your feedback. Best regards, Stu
