Both were released some time ago. Full changelog here: http://xcache.lighttpd.net/browser/tags/3.1.0/ChangeLog v.3.0.4 includes stability fixes and 3.1.0 includes PHP 5.5 support. Thank you.
I second this, because at the moment it's no longer possible to use XCache with the latest PHP : [blocks B ] dev-lang/php:5.5[opcache] ("dev-lang/php:5.5[opcache]" is blocking dev-php/xcache-3.0.3-r1) The 3.1.0 update should remove this blocking, since it allows for disabling the opcache in XCache in order to only use the user cache (sort of like what APCu does with APC).
Created attachment 365156 [details] xcache 3.1.0 ebuild I've attached the ebuild for 3.1.0 I've used for my servers : * Updated to 3.1.0 * Removed the virtual apache dependency (I use nginx+fpm!) * Removed the conflict with PHP 5.5's opcache
Hi, Why has this ebuild still not be integrated in portage tree? Regards, Gaëtan
Any progress regarding this bug...?
I resorted to installing layman and bgo-overlay to get xcache. What is holding up this bump?
Another ping. I maintain a Gentoo vps and it would really help to bump the newer versions in the tree. This bug has been open for some time now, isn't it time for someone to take a look into it? I'm pretty sure I'm not the only one needing this.
Few months have passed since my last reply. Isn't someone going to take care after this bug?
Versions 3.1.2 and 3.2.0 with PHP 5.6 support were released today. I hope someone takes cares of this bug.
I've just added 3.0.4 and 3.1.2 to my overlay. I'm going to test 3.2.0 now. Anyone in a hurry could test them and provide some feedback. If there are no major issues, I'll add them to the tree soon.
14:12 < irker162> gentoo-x86: jmbsvicetto dev-php/xcache: dev-php/xcache add 3.0.4, 3.1.2 and 3.2.0 releases - fixes bug 491358. Done
Thanks for the commit in portage. The xcache developer has released a newer 3.2.0 version, because of a version mismatch in a file. Thus, it seems that the checksum fails, so the checksum file must be updated for the newer 3.2.0 package.
The Xcache diagnosis page states that the coverager module is not recommended to be enabled in production servers. So, I set --enable-xcache-coverager to --disable-xcache-coverager in the xcache ebuild and recompiled. After restarting Apache, the diagnosis page is all green now. For some reason, the ini directive xcache.coverager="Off" in xcache.ini does not work.
(In reply to Vasilis Lourdas from comment #12) > The Xcache diagnosis page states that the coverager module is not > recommended to be enabled in production servers. So, I set > --enable-xcache-coverager to --disable-xcache-coverager in the xcache ebuild > and recompiled. After restarting Apache, the diagnosis page is all green > now. For some reason, the ini directive xcache.coverager="Off" in xcache.ini > does not work. Forgot to ask if this could be merged in the ebuild. Thanks.
Let me know if you have any more problems! commit 90d6b363a5e12a3de93aa91d77447344948147ce Author: Michael Orlitzky <mjo@gentoo.org> Date: Sun Jul 10 18:48:03 2016 -0400 dev-php/xcache: new revision for v3.2.0. The main reason for this revision is to make the coverager module optional. It is now hidden behind the USE=coverage flag and is not enabled by default (it is not recommended for production servers). At the same time, the ebuild was upgraded to EAPI=6 and now uses the newer revision php-ext-source-r3.eclass. Finally, the htdocs/ admin interface directory was moved out of /usr/share/php and into /usr/share/xcache, which is more appropriate. Two minor repoman warnings were also corrected. Gentoo-Bug: 491358 Package-Manager: portage-2.2.28 dev-php/xcache/metadata.xml | 7 ++++ dev-php/xcache/xcache-3.2.0-r1.ebuild | 64 +++++++++++++++++++++++++++++++++++ dev-php/xcache/xcache-3.2.0.ebuild | 60 -------------------------------- 3 files changed, 71 insertions(+), 60 deletions(-)
