Summary: | Emerging php-4.4.7 & php-5.2.2-r1 at the same time puts php-5.2.2-r1 at both places | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Uli Wolf <uli.wolf> |
Component: | [OLD] Server | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Uli Wolf
2007-07-11 09:22:51 UTC
That's what php-select from app-admin/php-toolkit is for. You can only have one symlink to PHP at a time. :P http://www.gentoo.org/proj/en/php/php-upgrading.xml#doc_chap3_sect5 Thanks for trying to resolve my Bugreport, but i think you misunderstood the Problem. I didn't try to execute /usr/bin/php but the binary itself (/usr/lib/php5/bin/php or /usr/lib/php4/bin/php) to which the symlink /usr/bin/php would point to. If I execute the binary /usr/lib/php4/bin/php with the switch -v it shouldn't report PHP5 or am i wrong? And if re-emerge PHP4 afterwards, then /usr/lib/php5/bin/php reports, that it's a PHP4? Is is simply the wrong Output from the binary? Or is the php4 Binary in /usr/lib/php4 and /usr/lib/php5? Hope you could clearify this for me. Sorry, really no clue what's this about, what you are describing is impossible AFAICT. Either unmerge both ebuilds, stick collision-protect to features and check for yourself that nothing gets overwritten anywhere, or if it gets overwritten, then attach completely compile.log for both ebuilds here. The Problem was the previously installed php4, which was only reemerged, but not removed and reinstalled. php5 removed php4, made a symlink from php4 to php5 (haven't seen this) and installed itself. So php4 = php5... => problem solved: emerge --unmerge php emerge -avD '=dev-lang/php-4*' '=dev-lang/php-5*' and everything was ok... Sorry for this. I have overseen this... Thanks a lot for testing. :) |