From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: esethome
Date: Fri, 15 Jun 2012 09:16:27 -0400 [thread overview]
Message-ID: <4FDB35AB.8060200@gentoo.org> (raw)
In-Reply-To: <201206131651.12444.vapier@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 13/06/12 04:51 PM, Mike Frysinger wrote:
> On Wednesday 13 June 2012 15:35:40 Ian Stakenvicius wrote:
>> --- user.eclass [some timestamp] +++
>> user.eclass.esethome [some other timestamp] @@ -388,3 +388,63
>> @@ }
>>
>> fi + +# @FUNCTION: esethome
>
> has to be inside the giant if block. so put this above the "fi".
>
>> +# @USAGE: <user> <homedir> +# @DESCRIPTION: +# Update the home
>> directory in a platform-agnostic way. +# Required parameters is
>> the username and the new home directory. +# Specify -1 if you
>> want to set home to the enewuser default +# of /dev/null. +# If
>> the new home directory does not exist, it is created. +# Any
>> previously existing home directory is NOT moved. +esethome() { +
>> _assert_pkg_ebuild_phase ${FUNCNAME} + + # get the
>> username + local euser=$1; shift + if [[ -z ${euser}
>> ]] ; then + eerror "No username specified !" +
>> die "Cannot call esethome without a username" + fi + +
>> # lets see if the username already exists + if [[ ! -n
>> $(egetent passwd "${euser}") ]] ; then
>
> "! -n" -> "-z" -mike
So outside of syntax issues like above, anyone have any issues with my
adding this to user.eclass ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iF4EAREIAAYFAk/bNaoACgkQ2ugaI38ACPAFRgEApwLkrsqSIW0nVK4l/dUTRzV9
ijEnbfa+BLc1skwfW4QA+gKgpmsz/K5VqXnVWyXocGqO98RYJL8lL3qm7k0Hs6uZ
=9i38
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-06-15 13:17 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 [this message]
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
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=4FDB35AB.8060200@gentoo.org \
--to=axs@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