[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] [PATCH] use.desc: Improve description of USE=test
From:       Zac Medico <zmedico () gentoo ! org>
Date:       2018-08-26 7:21:59
Message-ID: 5cf20754-45f9-0ef3-1ea1-4aff29de87d8 () gentoo ! org
[Download RAW message or body]

[Attachment #2 (multipart/mixed)]


On 08/26/2018 12:14 AM, Zac Medico wrote:
> On 08/24/2018 04:56 PM, Francesco Riosa wrote:
> > 
> > 
> > Il giorno sab 25 ago 2018 alle ore 01:45 Zac Medico <zmedico@gentoo.org
> > <mailto:zmedico@gentoo.org>> ha scritto:
> > 
> > On 08/24/2018 04:14 PM, Francesco Riosa wrote:
> > > 
> > > Il 24/08/18 19:08, Mike Gilbert ha scritto:
> > > > On Fri, Aug 24, 2018 at 10:45 AM Kent Fredric <kentnl@gentoo.org
> > <mailto:kentnl@gentoo.org>> wrote:
> > > > > On Fri, 24 Aug 2018 10:27:01 -0400
> > > > > Mike Gilbert <floppym@gentoo.org <mailto:floppym@gentoo.org>> wrote:
> > > > > 
> > > > > > If you want to define behavior that can be relied upon in
> > ebuilds, it
> > > > > > should be specified in PMS. PMS does not define any meaning for the
> > > > > > "test" USE flag.
> > > > > We should eschew idealism about how the world *should* behave,
> > and avoid
> > > > > making portage a steaming garbage heap in order to comply with a
> > > > > terrible PMS specification of a heavily used feature.
> > > > Portage still works just fine for most people who would enable
> > > > FEATURES=test. Stop exaggerating.
> > > > 
> > > People enabling FEATURES=test on most but not all packages had some
> > > troubles and they need to disable them in both package.{env,use}
> > > I'd like to have a flag to reinstate the previous portage
> > behaviour, but
> > > that's probably too late
> > 
> > Would a FEATURES setting that implies RESTRICT="!test? ( test )" for all
> > ebuilds do what you want?
> > 
> > 
> > "want" is too much,
> > but it would have been pleasant to have something to keep portage
> > dependancies working as before.
> > "testrespectuse" or "usetestrespectfeatures" come to mind or another
> > command line option.
> 
> Maybe you are not using the latest version of portage? The current
> behavior with sys-apps/portage-2.3.48 seems pretty sane to me, for
> example see this behavior with dev-python/setuptools-40.0.0 which has
> empty RESTRICT:
> 
> $ emerge -pvq --nodeps setuptools
> [ebuild   R   ] dev-python/setuptools-40.0.0  USE="-test" PYTHON_TARGETS="pypy \
> pypy3 python2_7 python3_4 python3_5 python3_6 python3_7"  $ FEATURES=test emerge \
> -pvq --nodeps setuptools [ebuild   R   ] dev-python/setuptools-40.0.0  USE="test*" \
> PYTHON_TARGETS="pypy pypy3 python2_7 python3_4 python3_5 python3_6 python3_7"  $ \
> FEATURES=test USE=-test emerge -pvq --nodeps setuptools [ebuild   R   ] \
> dev-python/setuptools-40.0.0  USE="-test" PYTHON_TARGETS="pypy pypy3 python2_7 \
> python3_4 python3_5 python3_6 python3_7" 

Oh, I see that src_test runs even with USE=-test there, so I see why
people are complaining. Anyway, an implicit RESTRICT="!test? ( test )"
setting would solve that.
-- 
Thanks,
Zac


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]