On wto, 2017-04-11 at 12:47 -0500, James Potts wrote:
> As another user, I have an interesting thought: Keep *_TARGETS and
> *_COMPAT, but add useflags called "[python|php|ruby]-compat-testing",
> which is at least use.stable.mask'ed (possibly straight-up
> use.mask'ed), to any ebuild that uses *_
As another user, I have an interesting thought: Keep *_TARGETS and
*_COMPAT, but add useflags called "[python|php|ruby]-compat-testing",
which is at least use.stable.mask'ed (possibly straight-up
use.mask'ed), to any ebuild that uses *_COMPAT. Setting the
appropriate useflag would allow such ebui
William L. Thomson Jr. posted on Mon, 10 Apr 2017 17:58:57 -0400 as
excerpted:
> When did changing targets to only have 1 version of Ruby, or 2 pythons
> becoming hacking. I do like how it was phrased. It shows right there the
> issue. If ANYONE has to hack around it, it sucks
>
>> Well, you
