# Brian Evans <grknight@gentoo.org> ( 1 Oct 2014 ) # Masked for removal in 30 days. # Broken on >=dev-lang/php-5.4. Replace with dev-php/xcache, # dev-php/pecl-zendopcache, or dev-lang/php[opcache]. # If you need pecl-apc's variable storage use dev-php/pecl-apcu. dev-php/eaccelerator dev-php/pecl-apc # Brian Evans <grknight@gentoo.org> ( 1 Oct 2014 ) # Masked for removal in 30 days. # Broken on >=dev-lang/php-5.4. No replacements known. dev-php/adodb-ext dev-php/pecl-id3 dev-php/pecl-mogilefs dev-php/pecl-sca_sdo dev-php/suhosin
Well, for dev-php/suhosin "no replacements known" is no longer the case: See Bug #520178. Or are there known problems with suhosin for PHP >= 5.4 ? https://bugs.gentoo.org/show_bug.cgi?id=520178
FYI: eaccelerator works fine in 5.4 if taken from git (overlay "raw") and works best.
1) How is pecl-apc broken on PHP 5.4? Can you provide more info? I've been using APC with PHP 5.4 in production for years now in a medium size website with no issues. It's stable as far as I can tell. It may be optional for PHP 5.5, but I it works fine for php<=5.4. So, why is it being removed? 2) Dropping both pecl-apc and eaccelerator would leave no opcode cache for PHP 5.3 on portage. Yes, I know that PHP 5.3 is super-old, but I have systems that still have to run legacy code which needs it - I suspect I'm not the only one. 3) Lastly, AFAIK, pecl-apcu is not yet a 100% stable replacement for pecl-apc user storage. Last time I tried it, apache was segfaulting with it and up to at least 4.0.4 it couldn't be used as a drop-in replacement (for example, see https://github.com/krakjoe/apcu/issues/41). This may have been fixed on 4.0.6 which I didn't had the chance to test yet, but also is masked on portage. So, I'm not sure if I'm the only one to need this, but it would be great if we could keep pecl-apc at least for PHP <= 5.4.
(In reply to Denis Kaganovich from comment #2) > FYI: eaccelerator works fine in 5.4 if taken from git (overlay "raw") and > works best. Eaccelerator is pretty much a dead project. That there is a branch in git that works with an already outdated PHP version does not really matter. (In reply to Paulo M from comment #3) > 2) Dropping both pecl-apc and eaccelerator would leave no opcode cache for > PHP 5.3 on portage. Yes, I know that PHP 5.3 is super-old, but I have > systems that still have to run legacy code which needs it - I suspect I'm > not the only one. We are working hard on removing PHP 5.3 from the tree as it is, as you say, super-old and receives no security fixes. > So, I'm not sure if I'm the only one to need this, but it would be great if > we could keep pecl-apc at least for PHP <= 5.4. Considering the age of 5.4, and how easy it is to migrate now, I would not rely on being able to stay with 5.4 that much longer. You should really consider upgrading as soon as possible. But we'll discuss if we keep pecl-apc a little while longer or not.
(In reply to Paulo M from comment #3) > 1) How is pecl-apc broken on PHP 5.4? Can you provide more info? I've been > using APC with PHP 5.4 in production for years now in a medium size website > with no issues. It's stable as far as I can tell. It may be optional for PHP > 5.5, but I it works fine for php<=5.4. So, why is it being removed? > I have personally experienced data corruption with pecl-apc on php 5.4. I don't recall all of the details but I kind of remember possible cross-session data leakage on my production box. I moved to pecl-zendopcache and it went away. This was when 5.4 support was added to pecl-apc and there has been no changes since then. Since pecl-apc is no longer developed, the only choice was to find an alternative.
> I have personally experienced data corruption with pecl-apc on php 5.4. I > don't recall all of the details but I kind of remember possible > cross-session data leakage on my production box. I moved to > pecl-zendopcache and it went away. I'm not sure what you mean with cross-session? Anyhow, I make a fairly heavy use of pecl-apc (3.1.13) with PHP 5.4 (both opcache and user data) in a website with 30M+ requests/month - never traced any issues to pecl-apc. > This was when 5.4 support was added to pecl-apc and there has been no > changes since then. Support for 5.4 seems to have been added back on 3.1.10 - can't speak for that particular release. Current version is 3.1.13 and it's about 2 years old - no major issues AFAIK.
(In reply to Ole Markus With from comment #4) > > We are working hard on removing PHP 5.3 from the tree as it is, as you say, > super-old and receives no security fixes. > But we'll discuss if we keep pecl-apc a little while longer or not. It would be great if we could at least keep it around until PHP 5.3 is dropped. In fact, it works perfectly fine for PHP 5.4 (AFAIK), so if it was up to me, I would keep it around until PHP 5.4 is also dropped. As I mentioned earlier, my experience is pecl-acpu is not mature enough yet for production replacement of pecl-apc on variable storage.
done
