Since eselect support has been added to PHP 5.3, pecl-memcache will not emerge. Portage complains that PHP is blocking pecl-memcache. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge php 3. emerge pecl-memcache Actual Results: Calculating dependencies... done! [ebuild N ] dev-php5/pecl-memcache-2.2.5 USE="session" 0 kB [blocks B ] =dev-lang/php-5.3.5 ("=dev-lang/php-5.3.5" is blocking dev-php5/pecl-memcache-2.2.5) Expected Results: pecl-memcache will be installed. If I use --no-deps for the emerge, the pecl-memcache build complains that it can't find php-config. php-config is in the path, I am not sure what the current ebuild is doing there. Manually installing pecl-memcache from PECL works fine.
If you are going to use the latest php, then you need to use the latest pecl-memcache too. Keywords: php-5.3.5[5.3]: amd64 arm hppa ppc ppc64 x86 ~alpha Keywords: pecl-memcache-3.0.5-r1[0]: amd64 hppa ppc64 x86 ~ppc So, why pecl-memcache-2.2.5 is being pulled in...no idea. Please post your emerge --info and check /etc/portage/package.* files for php/pecl stuff.
pecl-memcache 3 is fundamentally broken and should not even be in portage IMO. This is well documented on the memcached mailing list and a generally known fact by people that use PHP and memcached on any site that has any kind of volume.
In fact, pecl-memcache 3 is still marked as beta from upstream. Why would you have a "stable" package in portage of a package that developers still consider beta?
Right, I can't answer that. But, I can answer that the "3" series is where PHP minor slotting support came in, so the "2" series definately will not work with minor slotted PHP versions. *pecl-memcache-3.0.5-r1 (08 Oct 2010) 08 Oct 2010; <olemarkus@gentoo.org> +pecl-memcache-3.0.5-r1.ebuild: Added version supporting minor version slotting So, I can only _assume_ that you have the "3" series masked in package.mask based on non-direct answers to my queries. The PHP team will have to answer your concerns about stability... (but it is not uncommon for Gentoo's "stable" tree to diverge from upstream's definition based on differing criteria, etc)
Perhaps there are two issues really: 1. Should pecl-memcache 3 be stable? Perhaps debatable. 2. pecl-memcache 2 should be supported in the slotted PHP. Since the most recent version of 2.x was released at the same time as 3.x I see no reason it is not supported in slotted PHP.
(In reply to comment #5) > Perhaps there are two issues really: > > 1. Should pecl-memcache 3 be stable? Perhaps debatable. The 3.x branch have gone through normal testing in ~arch and was stabilised after a stabilisation request (bug 337218 and follow-up). This despite my warning that memcache 3.0 was considered "beta". > > 2. pecl-memcache 2 should be supported in the slotted PHP. Since the most > recent version of 2.x was released at the same time as 3.x I see no reason it > is not supported in slotted PHP. > We probably missed this fact during our ebuild upgrade-to-minorvs sweep. I committed a minor version slotting-supported ebuild now
