1 |
On 31/07/2013 17:36, Canek Peláez Valdés wrote: |
2 |
> No, because the *exact same* situation occurs for Bash completion |
3 |
> scripts... and logrotate scripts... and cron jobs... and... |
4 |
> |
5 |
> The devs decided (and I agree with them) that the important thing is |
6 |
> to cover the necessities of the majority of users and to have |
7 |
> reasonable default settings. Therefore, having USE flags for |
8 |
> bash_complete, and logrotate, and crond, and systemd, and OpenRC, and |
9 |
> whatever else you want to throw in the mix is overkill and a |
10 |
> maintenance nightmare. Not to mention that they will require a full |
11 |
> rebuild every time you changed one of those flags. And the packages |
12 |
> (in general) will not care about those tiny files; they will work fine |
13 |
> with all of them installed, no matter if you don't use Bash |
14 |
> completion, nor logrotate, nor crond, nor systemd nor OpenRC. |
15 |
> |
16 |
> So, those files are installed unconditionally. And that's the smart |
17 |
> thing to do, since most users will not even care about any of them. |
18 |
|
19 |
|
20 |
Folk will get MUCH larger savings if they mask html help/doc files from |
21 |
being installed. Those things get to be huge. |
22 |
|
23 |
Whinging about systemd binaries being installed is valid, but whinging |
24 |
about some data files is not. Anyone who does is letting their OCD show |
25 |
in ways they really should be keeping private. |
26 |
|
27 |
Unless the system is embedded in which case a lot more than units are |
28 |
going to be masked out |
29 |
|
30 |
|
31 |
-- |
32 |
Alan McKinnon |
33 |
alan.mckinnon@×××××.com |