On Sat, May 11, 2013 at 6:30 PM, Joe Watkins wrote:
> On 05/11/2013 11:10 AM, Joe Watkins wrote:
>
>> On 05/10/2013 08:54 PM, Christopher Jones wrote:
>>
>>>
>>>
>>> On 05/09/2013 05:02 AM, Pierre Schmitz wrote:
>>>
Hi,
I am testing PHP 5.5 atm and how we can package it for Arch Li
On 05/11/2013 11:10 AM, Joe Watkins wrote:
On 05/10/2013 08:54 PM, Christopher Jones wrote:
On 05/09/2013 05:02 AM, Pierre Schmitz wrote:
Hi,
I am testing PHP 5.5 atm and how we can package it for Arch Linux and
provide an upgrade path for users. The RC1 looks pretty solid so far.
As the ne
On 05/10/2013 08:54 PM, Christopher Jones wrote:
On 05/09/2013 05:02 AM, Pierre Schmitz wrote:
Hi,
I am testing PHP 5.5 atm and how we can package it for Arch Linux and
provide an upgrade path for users. The RC1 looks pretty solid so far.
As the new opcache does not provide a user cache to s
On 05/09/2013 05:02 AM, Pierre Schmitz wrote:
Hi,
I am testing PHP 5.5 atm and how we can package it for Arch Linux and
provide an upgrade path for users. The RC1 looks pretty solid so far.
As the new opcache does not provide a user cache to store custom
variables, I would be glad if you coul
Hey:
besides APCu, you can also have a try with :
https://github.com/laruence/yac :)
thanks
On Thu, May 9, 2013 at 8:02 PM, Pierre Schmitz wrote:
> Hi,
>
> I am testing PHP 5.5 atm and how we can package it for Arch Linux and
> provide an upgrade path for users. The RC1 looks pretty
I'm also very keen to understand the expected upgrade path, but from the
perspective of a PHP developer supporting some large bespoke applications
that rely heavily both on opcode caching and the user-caching functionality
of APC.
Is APCu the agreed best path for systems that currently use APC's u
