| 1 |
On Fri, Jul 20, 2012 at 6:23 PM, Ian Stakenvicius <axs@g.o> wrote: |
| 2 |
> enewuser won't create a home directory if you don't specify one (ie |
| 3 |
> it's set to /dev/null or it's unset). Also, you can use 'esethome' to |
| 4 |
> set the home directory to an existing directory. With both of these |
| 5 |
> options I don't think that a --do-not-create-homedir option is necessary. |
| 6 |
|
| 7 |
Well, with this approach there will now be three separate code blocks, |
| 8 |
just to create user's home directory: enewuser in pkg_preinst(), |
| 9 |
fperms / fowners in src_install(), and esethome in pkg_postinst(). |
| 10 |
Changing permissions as suggested by Kevin Pyle [1] looks more |
| 11 |
attractive then, since everything is in one code block. Moreover, if |
| 12 |
you want to keep the same semantics with esethome (only set the home |
| 13 |
directory when the user is created), you will need to keep a variable |
| 14 |
across ebuild phases. Also, it looks like pkg_postinst() is on the way |
| 15 |
out [2]. All-in-all, I think that a --do-not-create-homedir (or a |
| 16 |
shorter equivalent) is a good idea. |
| 17 |
|
| 18 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=395961#c1 |
| 19 |
[2] http://archives.gentoo.org/gentoo-dev/msg_ed43ed0df212ea26ef953fb061e9e860.xml |
| 20 |
|
| 21 |
-- |
| 22 |
Maxim Kammerer |
| 23 |
Liberté Linux: http://dee.su/liberte |
Archives