Gentoo Archives: gentoo-dev

From: Daniel Campbell <zlg@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] "Lazy" use flags?
Date: Wed, 10 Feb 2016 03:29:54
Message-Id: 56BAAEA7.1080809@gentoo.org
In Reply to: Re: [gentoo-dev] "Lazy" use flags? by Gordon Pettey
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA256
3
4 On 02/09/2016 07:08 PM, Gordon Pettey wrote:
5 >
6 > On Tue, Feb 9, 2016 at 7:19 AM, Kent Fredric
7 > <kentfredric@×××××.com <mailto:kentfredric@×××××.com>> wrote:
8 >
9 > On 10 February 2016 at 02:14, Daniel Campbell <zlg@g.o
10 > <mailto:zlg@g.o>> wrote:
11 >> Another concern, though, is it'd result in something similar.
12 >> Instead of "cat/foo bar baz" and later removing 'baz', you'd have
13 >> "cat/foo bar ~baz" (with '~baz' as 'enable this if you need to').
14 >> You'd still have cruft left in your p.use file, and it would
15 >> achieve the same result as a well-commented file.
16 >
17 >
18 > Granted you'd still have the cruft in your config files, but it
19 > would become mostly-harmless cruft, not cruft that caused needless
20 > dependencies to get pulled into the dependency tree as a
21 > side-effect.
22 >
23 > And because it would be "only as needed", you could afford to use
24 > some of those "only if needed" useflags in a more global manner.
25 >
26 > For instance, I really don't want to globally define PYTHON_TARGETS
27 > to include python2_7, because it will simply install a lot of
28 > extra things I know I don't need.
29 >
30 > But if I could globally define something to the effect of
31 > "anything that wants python2.7 support can have it", then that's
32 > acceptable globally, because the effect would still turn things on
33 > automatically on a per-page level, not at a global level.
34 >
35 > So you could achieve the same results with much less syntax and
36 > much less effort.
37 >
38 >
39 > A distinct behavior for +USE (as opposed to -USE and USE) would
40 > fit better than "~USE" IMHO, where the plus means "add if (and only
41 > if) required" and would cascade through dependencies, so if I merge
42 > e.g. app-portage/pfl with USE="+PYTHON_TARGETS_PYTHON2_7" it would
43 > apply that to dependencies as required. ~USE might fit for
44 > something like "~PYTHON_TARGETS_PYTHON3", where it would select the
45 > greatest flag matching that prefix, and would therefore
46 > automatically keep packages that have 3_2, 3_3, 3_4, 3_5 using
47 > whatever is the latest unmasked flag. Could potentially combine the
48 > prefixes, e.g. "~+PYTHON_TARGETS_PYTHON3" to both select the
49 > greatest python version AND cascade to dependencies.
50
51 The ~ was just a spitballed idea. It's really not important *what* the
52 symbol is, it's just that one would be required.
53
54 - --
55 Daniel Campbell - Gentoo Developer
56 OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
57 fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
58 -----BEGIN PGP SIGNATURE-----
59 Version: GnuPG v2
60
61 iQIcBAEBCAAGBQJWuq6mAAoJEAEkDpRQOeFwiGsQANMRonEdPVxs5wgG2XFB3bMf
62 +jTirnBZX0fH4wwaWy7eN5n1oaivepcup7XjUkiXuoqdyZmvZrb1ttwU/vrjaDZn
63 82rpP+7s9gNqSphifhGcf/EHTZo49VMZUEOBNElj0YtbEa3bcjG/vCpCgxnPuhVr
64 7LxuTtT0pDZd1mqMBLi+g5XYmDSfls2T2PWO3formcPYs5B3Xf4Dkc2jWEl7mEsB
65 neDtxkQoXkkuHX3y3uCwXb0KbGKEMenIA+1XiPP9P7nDSaagW+V0DXUWP5aCjTxB
66 csgiOrOdLEO1305eOkk7kxxoZIRoEgvtlSIA5G0R38+23A0Nwo/F0KV3hMjyBcbi
67 S6QuMrvwCgWiUIjgzd0zbI1+81EaHErn5zb6asdj78SaC5nzIbmRdw/zI+s4RIm0
68 8rw6RBsnDsP4Iah/kJHqMBdtDA7my7ImWKkKuWtAfeJfrYheDMb/NwMfl2L7/hIY
69 jKa0YuZ8P0TnU5xROFlIyXUILXMK/be5KA7RSQe16UMNGLsJLJ/5KBv2KQbJ2fqX
70 DBQG/780jZBNRAVFRimJ4v1S6g/+BJixN6ajZBe2tBjCV70ina7uL5H1K7cenvE5
71 0U2M0yl/K9QmEOJQoaR2iwTQL4fbRyr1ntbvlHWwE82rMKdQO2FwJxBj2yhEWELh
72 CAlwuL8k7LaFGVoQhQhb
73 =mkla
74 -----END PGP SIGNATURE-----

Replies

Subject Author
Re: [gentoo-dev] "Lazy" use flags? William Hubbs <williamh@g.o>