1 |
hasufell <hasufell@g.o> wrote: |
2 |
> |
3 |
> On 01/27/2014 12:26 AM, William Hubbs wrote: |
4 |
>> |
5 |
>> No, starting with USE="-*" is very dangerous. |
6 |
> |
7 |
> That's nonsense imo |
8 |
|
9 |
No, William is completely right. |
10 |
|
11 |
> and I use that setup on multiple servers/routers without any issues. |
12 |
|
13 |
No one doubts that it is *possible* to add the correct USE for |
14 |
every single package manually, but it is not a good idea to hide |
15 |
the recommended defaults. |
16 |
|
17 |
> It makes sense because you have the most minimal setup possible |
18 |
|
19 |
This is not true, to start with: For instance, USE=minimal will |
20 |
usually choose a more minimal setup. |
21 |
With "-*" you will actually *disable* the default USE=minimal |
22 |
for e.g. www-client/firefox, x11-apps/startx, sys-block/blocks, |
23 |
dev-db/unixODBC, ... and thus get a setup which is even larger |
24 |
than the recommended default. |
25 |
|
26 |
> most minimal codepaths possible which reduces exposure to bugs. |
27 |
|
28 |
No, you usually get less tested (and by upstream considered untypical) |
29 |
codepaths which actually increases the probability to hit a bug |
30 |
nobody did hit/test yet. |
31 |
|
32 |
The USE="-*" approach was reasonable before EAPI=1 was introduced: |
33 |
In these days, unusual codepaths would have been set by "negative" |
34 |
USE-flags, e.g. IUSE="nocxx" for gcc. |
35 |
Nowadays, the upstream-recommended codepaths are set by default-USE-Flags |
36 |
in the ebuild, i.e. now the same is called IUSE="+cxx" in gcc. |
37 |
Using -* you disable such defaults which are usually there for a |
38 |
good reason. |
39 |
|
40 |
Of course, if you know and care what every single USE-flags for every |
41 |
single package does, it does not matter much which approach you take, |
42 |
but I would guess that even in this case you need more exceptions |
43 |
in /etc/portage/package.use with USE="-*" than with USE="". |
44 |
|
45 |
Moreover, even for updates, it happens occassionally that a package |
46 |
gets an additional USE-flag, whose default is then usually chosen in |
47 |
such a way as the behaviour was before - so you risk dropping |
48 |
crucial behaviour on updates if you are not very careful. |