From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SesNK-00073n-US for garchives@archives.gentoo.org; Wed, 13 Jun 2012 18:33:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5A15DE06D7; Wed, 13 Jun 2012 18:32:48 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 7BFCDE0652 for ; Wed, 13 Jun 2012 18:32:09 +0000 (UTC) Received: from [192.168.1.145] (CPE002401f30b73-CM001cea3ddad8.cpe.net.cable.rogers.com [99.240.69.152]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id D3CAF1B4023 for ; Wed, 13 Jun 2012 18:32:08 +0000 (UTC) Message-ID: <4FD8DCB6.4050207@gentoo.org> Date: Wed, 13 Jun 2012 14:32:22 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120511 Thunderbird/10.0.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: enewuser should force updates to shell and home References: <4FD8B910.3090606@gentoo.org> <20120613180931.GU20778@gentoo.org> In-Reply-To: <20120613180931.GU20778@gentoo.org> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: a2436772-aae6-4255-bfb7-211455289d65 X-Archives-Hash: 629ad6653baa1edb29cd75fb3f28f0c7 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 13/06/12 02:09 PM, Fabian Groffen wrote: > On 13-06-2012 12:00:16 -0400, 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. > > What if some admin purposely changed home or shell for a system > account? Would be quite annoying if every update would reset that, > wouldn't it? > > I considered this case, and that it might be more appropriate to duplicate 'enewuser' into a new call 'eforceuser' (or similar) which could be used instead of 'enewuser' in cases when the currently provided user settings should be forced. I decided against this as it seems also to make sense that users created by portage should be controlled by portage. I suppose probably the best means of handling this would be to somehow detect whether or not the current user settings are default and only apply the updates if they are; however a means of doing that (which would be transparent to the ebuild) is somewhat beyond my knowledge and abilities. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iF4EAREIAAYFAk/Y3LYACgkQ2ugaI38ACPCKKwEAsA2kiUEj2Cz5DyuKzlVUvqlq 9N7TH6cEUN7ahL6IIgoA/iiJRJ065vQguz5PmitWVugycdNhm/DCyGcL8j0abcgA =zd5h -----END PGP SIGNATURE-----