On Thu, Aug 22, 2013 at 1:30 PM, Ole Markus With
wrote:
> On 22/08/13 21:27, Zac Medico wrote:
>> On Thu, Aug 22, 2013 at 12:08 PM, Ole Markus With
>> wrote:
>>> However, now the time has come for php5.5 to be stabilised, and all is
>>> working great except that I cannot remove php_targets_php5-
On 22/08/13 21:27, Zac Medico wrote:
> On Thu, Aug 22, 2013 at 12:08 PM, Ole Markus With
> wrote:
>> However, now the time has come for php5.5 to be stabilised, and all is
>> working great except that I cannot remove php_targets_php5-5 from
>> use.stable.mask until all arches have stabilised php.
On Thu, Aug 22, 2013 at 12:08 PM, Ole Markus With wrote:
> However, now the time has come for php5.5 to be stabilised, and all is
> working great except that I cannot remove php_targets_php5-5 from
> use.stable.mask until all arches have stabilised php.
You could have separate use.stable.mask ent
Dnia 2013-08-22, o godz. 21:08:52
Ole Markus With napisał(a):
> However, now the time has come for php5.5 to be stabilised, and all is
> working great except that I cannot remove php_targets_php5-5 from
> use.stable.mask until all arches have stabilised php. For those arches
> with stable php5.5,
Hi,
It seems to be a pattern now to mask the language "target" USE flags
for unstable versions, such as python_targets_python3_3 and
php_targets_php5-5.
This is very handy since e.g I do not need two revisions of
dev-php/xdebug:
- one that can be stabilised, supporting stable php5.3 and php5.4an
