On Sun, 12 Feb 2017 16:07:37 +0100 Ulrich Mueller <[email protected]> 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 warning > in place since five years, so people had plenty of time to update > their ebuilds. Also the corresponding has_m32() was removed long ago. > > 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 seem to bring any advantage. The 5 years deprecation is irrelevant here: With C libraries, you deprecate a symbol/function for a few years then bump soname when dropping it. The equivalent here is removing it in a new EAPI after a deprecation period.
