1 |
Matt Turner posted on Fri, 27 Jan 2017 10:40:16 -0800 as excerpted: |
2 |
|
3 |
> On Fri, Jan 27, 2017 at 8:22 AM, Mike Gilbert <floppym@g.o> |
4 |
> wrote: |
5 |
>> On Fri, Jan 27, 2017 at 2:54 AM, Mart Raudsepp <leio@g.o> wrote: |
6 |
>>> Then there is no need to think about what is enabled globally or not. |
7 |
>>> Point being, use REQUIRED_USE sparingly, and rarely a good idea to |
8 |
>>> block things with common global USE flags, or demand a local USE flag |
9 |
>>> based on a default enabled global USE flag without locally USE |
10 |
>>> defaulting that global flag too - and other such cases. |
11 |
>> |
12 |
>> I didn't really mean for this to turn into a thread about the merits of |
13 |
>> REQUIRED_USE; in hindsight I should have left out that first sentence. |
14 |
>> |
15 |
>> Regardless of the REQUIRED_USE discussion, I don't think it makes sense |
16 |
>> to have berkdb and gdbm in USE in make.defaults. I would like to move |
17 |
>> them to IUSE defaults or package.use if necessary. |
18 |
> |
19 |
> I think you should feel free to proceed with such a change. |
20 |
> |
21 |
> FWIW, disabling these USE flags (and fortran) are among the first |
22 |
> changes I made to a new make.conf. |
23 |
|
24 |
TL;DR: see last sentence/paragraph. |
25 |
|
26 |
FWIW, changes like that, either at profile upgrade time (with over a |
27 |
decade on gentoo on the same system, both hardware and software |
28 |
incrementally updated over time, I've done a few of those in my time) or |
29 |
worse made arbitrarily to existing profiles, are a big reason I |
30 |
ultimately decided USE="-* ..." worked best for me. Because if I depend |
31 |
on the profile to make the decision for me, eventually that decision is |
32 |
going to change, and I'll have to dig into what and why and decide what I |
33 |
want to do in any case, so it's better to simply deal with all that up |
34 |
front, and USE="-* ..." is the way that's done on gentoo. |
35 |
|
36 |
That way, global changes to my USE flags are only made when I make them, |
37 |
and I'll generally know at least the high-level why (say an update from |
38 |
qt4/kde4 to qt5/plasma5, with requisite USE flag changes) in that case, |
39 |
instead of having to deduce someone else's reason from the git log. (I |
40 |
may still need to research the lower level why qt5/plasma5 require the |
41 |
new flags and decide whether I can/want/need to override, via manual |
42 |
semantic-desktop patchout or the like, potentially, but that's an |
43 |
entirely different focus that unlike global profile default-use changes |
44 |
the normal user won't need to deal with.) |
45 |
|
46 |
Not saying I disagree with the change, but please at least make it a new |
47 |
profile only change if at all possible, so as not to disturb existing |
48 |
users until they decide to switch profiles, at which point they should be |
49 |
expecting at least some level of system adjustment to the new profile. |
50 |
|
51 |
-- |
52 |
Duncan - List replies preferred. No HTML msgs. |
53 |
"Every nonfree program has a lord, a master -- |
54 |
and if you use the program, he is your master." Richard Stallman |