1 |
Hi, |
2 |
|
3 |
William Hubbs wrote: |
4 |
> I believe, back in the day we started this practice, portage did not |
5 |
> support --newuse or --changed-use, so there was no way to only update |
6 |
> packages that had changed or new use flags. In that situation, I |
7 |
> understand why we installed all of these add-on files unconditionally |
8 |
> and told users to use INSTALL_MASK if they wanted them not to be on |
9 |
> their systems. |
10 |
> |
11 |
> However, I feel that we should update our practice now since we have these |
12 |
> features available to us and to our users. |
13 |
> |
14 |
> In my previous thread about zsh, it was suggested that I could use the |
15 |
> zsh-completion use flag to control zsh-completion installation, and not |
16 |
> rdepend on zsh. This is now how pybugz is set up. |
17 |
|
18 |
Are we talking about an actual problem? |
19 |
|
20 |
Are these "add-on files" causing real problems? |
21 |
|
22 |
How many "add-on files" on an average system are really useless (=cruft |
23 |
files) for most people and how much disk space do they take up? |
24 |
|
25 |
|
26 |
Do you remember the discussion about "USE flag per init system"? It was |
27 |
decided to drop the systemd USE flag if it is only controlling the |
28 |
installation of systemd service files and we didn't want to introduce a |
29 |
USE flag per init system because it doesn't scale. |
30 |
|
31 |
Also, image you are on OpenRC and decide to switch to systemd. If we |
32 |
wouldn't install the service files on every system the user would have |
33 |
to re-emerge his/her whole system to switch. |
34 |
|
35 |
Following your argumentation we would add an exception for init systems. |
36 |
|
37 |
So which add-on files are left? Logrotate! Doesn't the same argument |
38 |
against USE flags for each init system applies to things like logrotate, |
39 |
too? If not, at least the same argument "if you switch your init system" |
40 |
applies: If you decide to start using logrotate you would have to |
41 |
re-emerge your packages just for a 1kb file... |
42 |
|
43 |
Add another exception for logrotate files? :) |
44 |
|
45 |
I guess that's not what you want. But do you see the problem? How would |
46 |
you decide for which files you want to add an exception? |
47 |
|
48 |
Do you want to discuss with cron users if their cronjobs are add-on |
49 |
files or not? |
50 |
|
51 |
Some packages are providing files for logwatch. I don't expect that many |
52 |
desktop user will use logwatch. But do you want to start a discussion |
53 |
with non-desktop users if it is worth to re-emerge a whole package for |
54 |
1kb additional files? |
55 |
|
56 |
Coming back to my first question: Why do you want to change the current |
57 |
situation? Are these "add-on files" causing any problems nowadays? |
58 |
|
59 |
Introducing another USE flag to control what INSTALL_MASK already do |
60 |
doesn't sound like a good way to go for me. |
61 |
|
62 |
But maybe I am not aware of a real problem you have with these "add-on |
63 |
files"... |
64 |
|
65 |
|
66 |
-Thomas |