1 |
On 6/13/2012 2:32 PM, Ian Stakenvicius wrote: |
2 |
> On 13/06/12 02:09 PM, Fabian Groffen wrote: |
3 |
>> On 13-06-2012 12:00:16 -0400, Ian Stakenvicius wrote: |
4 |
>>> Hey all - I'd like to propose that enewuser forces updates to a |
5 |
>>> user's home dir and shell whenever it is called, so that if this |
6 |
>>> changes with new versions of an ebuild it is dealt with |
7 |
>>> automatically rather than having to modify them in |
8 |
>>> pkg_postinst/pkg_setup directly. |
9 |
> |
10 |
>> What if some admin purposely changed home or shell for a system |
11 |
>> account? Would be quite annoying if every update would reset that, |
12 |
>> wouldn't it? |
13 |
> |
14 |
> |
15 |
> |
16 |
> |
17 |
> I considered this case, and that it might be more appropriate to |
18 |
> duplicate 'enewuser' into a new call 'eforceuser' (or similar) which |
19 |
> could be used instead of 'enewuser' in cases when the currently |
20 |
> provided user settings should be forced. |
21 |
> |
22 |
> I decided against this as it seems also to make sense that users |
23 |
> created by portage should be controlled by portage. |
24 |
> |
25 |
> I suppose probably the best means of handling this would be to somehow |
26 |
> detect whether or not the current user settings are default and only |
27 |
> apply the updates if they are; however a means of doing that (which |
28 |
> would be transparent to the ebuild) is somewhat beyond my knowledge |
29 |
> and abilities. |
30 |
> |
31 |
|
32 |
Just a thought: You could introduce a variable that would disable the |
33 |
forced updates. This could be set in make.conf by any users who prefer |
34 |
not to have their passwd database updated automatically. |