Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: Francesco Riosa <vivo75@×××××.com>, Zac Medico <zmedico@g.o>
Cc: gentoo development <gentoo-dev@l.g.o>, Mike Gilbert <floppym@g.o>
Subject: Re: [gentoo-dev] [PATCH] use.desc: Improve description of USE=test
Date: Sun, 26 Aug 2018 07:14:14
Message-Id: c49ccd82-46a2-3a09-2416-33127d180792@gentoo.org
In Reply to: Re: [gentoo-dev] [PATCH] use.desc: Improve description of USE=test by Francesco Riosa
1 On 08/24/2018 04:56 PM, Francesco Riosa wrote:
2 >
3 >
4 > Il giorno sab 25 ago 2018 alle ore 01:45 Zac Medico <zmedico@g.o
5 > <mailto:zmedico@g.o>> ha scritto:
6 >
7 > On 08/24/2018 04:14 PM, Francesco Riosa wrote:
8 > >
9 > > Il 24/08/18 19:08, Mike Gilbert ha scritto:
10 > >> On Fri, Aug 24, 2018 at 10:45 AM Kent Fredric <kentnl@g.o
11 > <mailto:kentnl@g.o>> wrote:
12 > >>> On Fri, 24 Aug 2018 10:27:01 -0400
13 > >>> Mike Gilbert <floppym@g.o <mailto:floppym@g.o>> wrote:
14 > >>>
15 > >>>> If you want to define behavior that can be relied upon in
16 > ebuilds, it
17 > >>>> should be specified in PMS. PMS does not define any meaning for the
18 > >>>> "test" USE flag.
19 > >>> We should eschew idealism about how the world *should* behave,
20 > and avoid
21 > >>> making portage a steaming garbage heap in order to comply with a
22 > >>> terrible PMS specification of a heavily used feature.
23 > >> Portage still works just fine for most people who would enable
24 > >> FEATURES=test. Stop exaggerating.
25 > >>
26 > > People enabling FEATURES=test on most but not all packages had some
27 > > troubles and they need to disable them in both package.{env,use}
28 > > I'd like to have a flag to reinstate the previous portage
29 > behaviour, but
30 > > that's probably too late
31 >
32 > Would a FEATURES setting that implies RESTRICT="!test? ( test )" for all
33 > ebuilds do what you want?
34 >
35 >
36 > "want" is too much,
37 > but it would have been pleasant to have something to keep portage
38 > dependancies working as before.
39 > "testrespectuse" or "usetestrespectfeatures" come to mind or another
40 > command line option.
41
42 Maybe you are not using the latest version of portage? The current
43 behavior with sys-apps/portage-2.3.48 seems pretty sane to me, for
44 example see this behavior with dev-python/setuptools-40.0.0 which has
45 empty RESTRICT:
46
47 $ emerge -pvq --nodeps setuptools
48 [ebuild R ] dev-python/setuptools-40.0.0 USE="-test" PYTHON_TARGETS="pypy pypy3 python2_7 python3_4 python3_5 python3_6 python3_7"
49 $ FEATURES=test emerge -pvq --nodeps setuptools
50 [ebuild R ] dev-python/setuptools-40.0.0 USE="test*" PYTHON_TARGETS="pypy pypy3 python2_7 python3_4 python3_5 python3_6 python3_7"
51 $ FEATURES=test USE=-test emerge -pvq --nodeps setuptools
52 [ebuild R ] dev-python/setuptools-40.0.0 USE="-test" PYTHON_TARGETS="pypy pypy3 python2_7 python3_4 python3_5 python3_6 python3_7"
53 --
54 Thanks,
55 Zac

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies