1 |
On Wed, 10 Feb 2016 02:19:54 +1300 |
2 |
Kent Fredric <kentfredric@×××××.com> wrote: |
3 |
|
4 |
> On 10 February 2016 at 02:14, Daniel Campbell <zlg@g.o> wrote: |
5 |
> > Another concern, though, is it'd result in something similar. |
6 |
> > Instead of "cat/foo bar baz" and later removing 'baz', you'd have |
7 |
> > "cat/foo bar ~baz" (with '~baz' as 'enable this if you need to'). |
8 |
> > You'd still have cruft left in your p.use file, and it would |
9 |
> > achieve the same result as a well-commented file. |
10 |
> |
11 |
> |
12 |
> Granted you'd still have the cruft in your config files, but it would |
13 |
> become mostly-harmless cruft, not cruft that caused needless |
14 |
> dependencies to get pulled into the dependency tree as a side-effect. |
15 |
> |
16 |
> And because it would be "only as needed", you could afford to use some |
17 |
> of those "only if needed" useflags in a more global manner. |
18 |
|
19 |
The question is whether you really need to specify the lazy use flag |
20 |
explicitly. I would say that any flag which user did not set |
21 |
explicitly to -baz or baz could be considered as lazy use flag. |
22 |
|
23 |
So if I'd have 'baz' set in /etc/portage/make.conf, |
24 |
/etc/portage/package.use, USE environment variable or other user |
25 |
configuration then I'd clearly want to turn on baz (globally or for |
26 |
specific packages). Portage would not change the use flag in this |
27 |
case (again globally or for particular packages only). |
28 |
|
29 |
On the other side, if I would not specify 'baz' in any of those user |
30 |
configurations (so it would be specified only in profile, ebuild or |
31 |
nowhere at all) then I most likely would not care about it therefore |
32 |
portage can enable or disable it as needed. |
33 |
|
34 |
BTW, what you are describing is essentially the same as in this bug: |
35 |
https://bugs.gentoo.org/show_bug.cgi?id=258371. It was also discussed |
36 |
on this list couple of times. I too would very much like to see it in |
37 |
portage. |
38 |
|
39 |
Robert |
40 |
|
41 |
|
42 |
-- |
43 |
Róbert Èeròanský |
44 |
E-mail: openhs@×××××××××.com |
45 |
Jabber: hs@××××××.sk |