1 |
On Fri, 2019-06-21 at 08:59 +0300, Andrew Savchenko wrote: |
2 |
> On Thu, 20 Jun 2019 16:32:56 +0200 Michał Górny wrote: |
3 |
> > On Thu, 2019-06-20 at 09:53 -0400, Brian Evans wrote: |
4 |
> > > On 6/9/2019 7:39 AM, Michał Górny wrote: |
5 |
> > > > +Tracking of user/group usage is done through dependencies. As |
6 |
> > > > long |
7 |
> > > > +as any installed package depends on a specific user/group |
8 |
> > > > package, |
9 |
> > > > +the respective user/group is assumed to be used. If no |
10 |
> > > > package |
11 |
> > > > +requiring the specific user/group is left, the package manager |
12 |
> > > > +automatically prunes the package clearly indicating it is no |
13 |
> > > > longer |
14 |
> > > > +used. |
15 |
> > > |
16 |
> > > You cannot know when a name is "no longer used". An |
17 |
> > > administrator could |
18 |
> > > have adopted a username for other purposes. |
19 |
> > |
20 |
> > That's why we don't remove the actual user/group. However, this is |
21 |
> > a valuable information to the administrator that no package is |
22 |
> > using |
23 |
> > the user/group in question. |
24 |
> |
25 |
> So how do you propose to clean them up? Or let user systems trash |
26 |
> with unused uids/gids? The GLEP 81 only mensions some possible |
27 |
> tooling for cleanup. Is there an implementation available? I don't |
28 |
> see it within proposed patch sets. |
29 |
> |
30 |
> This GLEP should not be accepted unless all necessary tools are |
31 |
> available including a cleanup tool. |
32 |
> |
33 |
> Best regards, |
34 |
> Andrew Savchenko |
35 |
|
36 |
Strongly disagree: |
37 |
|
38 |
1) User systems are already getting trashed. And apparently it's not a |
39 |
critical thing that prevents users from using Gentoo in practice. |
40 |
2) A cleanup tool at best will only tell you which files you need to |
41 |
check, randomly deleting files with orphaned uids/gids is not a good |
42 |
idea. |
43 |
3) This proposal strictly increases the quality of Gentoo. Don't let |
44 |
perfect be the enemy of the good. The fact that the problem isn't |
45 |
solved to 100% doesn't mean that a solution that gets us there 85% |
46 |
should be rejected. |
47 |
|
48 |
Strongly vote +1 to merge this now. |