From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: enewuser should force updates to shell and home
Date: Wed, 13 Jun 2012 21:22:12 +0300 [thread overview]
Message-ID: <4FD8DA54.9080005@gentoo.org> (raw)
In-Reply-To: <4FD8D991.4060704@gentoo.org>
On 06/13/2012 09:18 PM, Mike Gilbert wrote:
> On 6/13/2012 12:00 PM, Ian Stakenvicius wrote:
>> Hey all - I'd like to propose that enewuser forces updates to a user's
>> home dir and shell whenever it is called, so that if this changes with
>> new versions of an ebuild it is dealt with automatically rather than
>> having to modify them in pkg_postinst/pkg_setup directly.
>>
>
> Can you give an example of a case where modifying the home directory
> and/or shell is necessary? I don't really understand how this is useful.
package-1.2.3.ebuild creates user foobard with group foobard and sets
home to /dev/null
bug gets filed against package-1.2.3.ebuild that foobard needs a home or
it won't execute itself, and the maintainer changes the home to be
/var/lib/foobard in package-1.2.3-r1.ebuild
no change happens to passwd and the package continues to fail to run at all
like http://bugs.gentoo.org/420269
sed -i -e '/^foobard/s:/dev/null:/var/lib/foobard' "${ROOT}"/etc/passwd
in pkg_postinst() doesn't seem very nice solution :/
>
> Also, grobian raised a good point in that the sysadmin may have changed
> it manually. It might be better to ewarn and make the user deal with it.
>
i'd prefer argument to force the update, when the problem hits something
that 99,98% of users have installed, like sys-auth/polkit, an ewarn is
not adequate
- Samuli
next prev parent reply other threads:[~2012-06-13 18:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 16:00 [gentoo-dev] RFC: enewuser should force updates to shell and home Ian Stakenvicius
2012-06-13 17:19 ` Michał Górny
2012-06-13 17:21 ` Ian Stakenvicius
2012-06-13 18:45 ` Ian Stakenvicius
2012-06-13 18:47 ` Ian Stakenvicius
2012-06-13 18:09 ` Fabian Groffen
2012-06-13 18:32 ` Ian Stakenvicius
2012-06-13 18:56 ` Mike Gilbert
2012-06-13 19:04 ` Mike Frysinger
2012-06-13 19:11 ` Ian Stakenvicius
2012-06-13 19:14 ` Mike Frysinger
2012-06-13 19:35 ` [gentoo-dev] RFC: esethome Ian Stakenvicius
2012-06-13 20:51 ` Mike Frysinger
2012-06-15 13:16 ` Ian Stakenvicius
2012-06-15 13:27 ` Peter Stuge
2012-06-15 13:35 ` Ian Stakenvicius
2012-06-15 13:39 ` Fabian Groffen
2012-06-15 13:41 ` Peter Stuge
2012-06-15 13:53 ` Fabian Groffen
2012-06-15 14:05 ` Peter Stuge
2012-06-15 14:23 ` Mike Gilbert
2012-06-15 14:34 ` Peter Stuge
2012-06-13 18:18 ` [gentoo-dev] RFC: enewuser should force updates to shell and home Mike Gilbert
2012-06-13 18:22 ` Samuli Suominen [this message]
2012-06-13 18:27 ` Ian Stakenvicius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD8DA54.9080005@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox