On Sun, 12 Feb 2017 17:39:48 +0100
Ulrich Mueller wrote:
> > On Sun, 12 Feb 2017, Alexis Ballier wrote:
>
> >> Or do you have any concrete evidence that has_m64 is still used?
>
> > Nope. It is just that it is part of an API that we export and, since
> > we have easy
> On Sun, 12 Feb 2017, Alexis Ballier wrote:
>> Or do you have any concrete evidence that has_m64 is still used?
> Nope. It is just that it is part of an API that we export and, since
> we have easy means to drop it properly, why not doing so ? Esp. since
> dropping it "improperly" doesn't
On Sun, 12 Feb 2017 16:07:37 +0100
Ulrich Mueller wrote:
> > On Sun, 12 Feb 2017, Alexis Ballier wrote:
>
> > I think it'd be better to lock the removal with a new EAPI for
> > overlays / downstreams.
>
> That sounds like complete overkill here. There's a deprecation
> On Sun, 12 Feb 2017, Alexis Ballier wrote:
> I think it'd be better to lock the removal with a new EAPI for
> overlays / downstreams.
That sounds like complete overkill here. There's a deprecation warning
in place since five years, so people had plenty of time to update
their ebuilds. Also
On 02/12/2017 01:58 PM, Alexis Ballier wrote:
> On Sun, 12 Feb 2017 10:28:13 +0100
> Ulrich Mueller wrote:
>
>> See patch below. The has_m64 function is no longer used in the tree.
>
> I think it'd be better to lock the removal with a new EAPI for
> overlays / downstreams.
>
On Sun, 12 Feb 2017 10:28:13 +0100
Ulrich Mueller wrote:
> See patch below. The has_m64 function is no longer used in the tree.
I think it'd be better to lock the removal with a new EAPI for
overlays / downstreams.
See patch below. The has_m64 function is no longer used in the tree.
Unfortunately, we cannot get rid of the eutils inherit because it is
still used for eqawarn.
Ulrich
From 84334ae8abd85c7880e5a357ff8f71bc8bdb1eee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?=