1 |
On Tue, Feb 9, 2016 at 7:19 AM, Kent Fredric <kentfredric@×××××.com> wrote: |
2 |
|
3 |
> On 10 February 2016 at 02:14, Daniel Campbell <zlg@g.o> wrote: |
4 |
> > Another concern, though, is it'd result in something similar. Instead |
5 |
> > of "cat/foo bar baz" and later removing 'baz', you'd have "cat/foo bar |
6 |
> > ~baz" (with '~baz' as 'enable this if you need to'). You'd still have |
7 |
> > cruft left in your p.use file, and it would achieve the same result as |
8 |
> > a well-commented file. |
9 |
> |
10 |
> |
11 |
> Granted you'd still have the cruft in your config files, but it would |
12 |
> become mostly-harmless cruft, not cruft that caused needless |
13 |
> dependencies to get pulled into the dependency tree as a side-effect. |
14 |
> |
15 |
> And because it would be "only as needed", you could afford to use some |
16 |
> of those "only if needed" useflags in a more global manner. |
17 |
> |
18 |
> For instance, I really don't want to globally define PYTHON_TARGETS to |
19 |
> include python2_7, because it will simply install a lot of extra |
20 |
> things I know I don't need. |
21 |
> |
22 |
> But if I could globally define something to the effect of "anything |
23 |
> that wants python2.7 support can have it", then that's acceptable |
24 |
> globally, because the effect would still turn things on automatically |
25 |
> on a per-page level, not at a global level. |
26 |
> |
27 |
> So you could achieve the same results with much less syntax and much |
28 |
> less effort. |
29 |
> |
30 |
|
31 |
A distinct behavior for +USE (as opposed to -USE and USE) would fit better |
32 |
than "~USE" IMHO, where the plus means "add if (and only if) required" and |
33 |
would cascade through dependencies, so if I merge e.g. app-portage/pfl with |
34 |
USE="+PYTHON_TARGETS_PYTHON2_7" it would apply that to dependencies as |
35 |
required. ~USE might fit for something like "~PYTHON_TARGETS_PYTHON3", |
36 |
where it would select the greatest flag matching that prefix, and would |
37 |
therefore automatically keep packages that have 3_2, 3_3, 3_4, 3_5 using |
38 |
whatever is the latest unmasked flag. Could potentially combine the |
39 |
prefixes, e.g. "~+PYTHON_TARGETS_PYTHON3" to both select the greatest |
40 |
python version AND cascade to dependencies. |