1 |
On Sun, Mar 29, 2015 at 7:28 PM, William Hubbs <williamh@g.o> wrote: |
2 |
> On Mon, Mar 30, 2015 at 12:11:34AM +0200, Matthias Maier wrote: |
3 |
>> |
4 |
>> > Thoughts? |
5 |
>> |
6 |
>> One point in favor of the current practice (installing add-on files |
7 |
>> unconditionally) is the fact that you can basically do it for free - you |
8 |
>> neither have to depend on additional packages, nor is the presence of |
9 |
>> the add-on files a penalty in download time or storage. |
10 |
> |
11 |
> The add-on files i'm talking about are not specifically used by the |
12 |
> packages that install them. They are add-ons that hook the packages into |
13 |
> external functions, such as shell completions, logrotate files, xinetd |
14 |
> configurations, etc. |
15 |
> |
16 |
> The penalty is cruft on the users's systems when they don't use the |
17 |
> programs that read these files, such as app-admin/logrotate, |
18 |
> sys-apps/xinetd, etc. |
19 |
|
20 |
The problem is that if you don't install this stuff up-front you end |
21 |
up rebuilding half your system to install it later. |
22 |
|
23 |
I think the cleanest solution is to just install this stuff |
24 |
unconditionally, and users who really object to having it around can |
25 |
use INSTALL_MASK. It is just a couple of inodes, on a distro that by |
26 |
default sticks a dozen inodes for every package in the repository on |
27 |
their root partition. |
28 |
|
29 |
You suggested that the past policy was due to the lack of |
30 |
--changed-use in portage at the time, but this is not the case. That |
31 |
option has been around for a very long time. Maybe if it first came |
32 |
up for manpages or docs that might have been the case, but certainly |
33 |
not in more recent cases. |
34 |
|
35 |
Not everybody uses logrotate, xinetd, cron.d, and so on. It still |
36 |
makes sense to just install the files, since they passively sit there |
37 |
doing nothing in those cases. |
38 |
|
39 |
|
40 |
-- |
41 |
Rich |