1 |
On 18/03/2016 17:29, Stroller wrote: |
2 |
> |
3 |
>> On Fri, 18 March 2016, at 6:07 am, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
4 |
>> |
5 |
>> … |
6 |
>> USE flags enable and disable features of software at compile-time. Take |
7 |
>> for example a music player. Maybe it can store the metadata about your |
8 |
>> music in flat files, in sqlite, in mysql or postgres. Now you must make |
9 |
>> a choice where to put the flag. Maybe your music collection is HUGE and |
10 |
>> postgres is the best fit. |
11 |
>> |
12 |
>> If you add it to make.conf it becomes global and every piece of software |
13 |
>> that supports postgres will now be rebuilt to give postgres support. |
14 |
>> Maybe you don't need or want that. |
15 |
>> |
16 |
>> A flag like that is best put into package.use where it applies only to |
17 |
>> the package you list there. So postgres gets installed, the music player |
18 |
>> gets support and your MTA does not. |
19 |
> |
20 |
> To expand on this example, if `emerge -p` showed your music player had flags for mp3, mp4 and aac files, I would probably set those in /etc/make.conf, because I want all music and video players and converters to support these common file types. |
21 |
|
22 |
|
23 |
Good point. This is where judgement comes in - what can probably go in |
24 |
make.conf and what will be better in package.use. |
25 |
|
26 |
I normally put general things like a/v codecs and hardware features |
27 |
make.conf as I'm very likely into want it everywhere. If I use handbrake |
28 |
to make mkv and mp4 rips, then I probably want mplayer, dragon, vlc and |
29 |
all the other players to play them. Makes sense. |
30 |
|
31 |
Then there's that other thread today that mentioned wayland. Some bit of |
32 |
KDE must have it but you certainly don't want it global. |
33 |
|
34 |
So a judgement call; which quite incidentally is the thing we sysadmins |
35 |
get paid to have :-) |
36 |
|
37 |
|
38 |
-- |
39 |
Alan McKinnon |
40 |
alan.mckinnon@×××××.com |