On Fri, 2008-01-18 at 06:41 -0500, Mike Frysinger wrote:
> right, there is no way (by design) to force these settings on an already
> created user. if the old path really truly should not be the old value, you
> can do something like this in pkg_setup:
> if [[ $(egetent passwd user | cut -d: -f
On Friday 18 January 2008, Marius Mauch wrote:
> "Hanno Böck" <[EMAIL PROTECTED]> wrote:
> > What is the correct way to handle this? I'd suggest that enewuser might
> > get some "force"-parameter that tells it to delete and recreate the user
> > if it already exists. Thoughts?
>
> Tell the user to
On Fri, 18 Jan 2008 03:46:58 +0100
"Hanno Böck" <[EMAIL PROTECTED]> wrote:
> What is the correct way to handle this? I'd suggest that enewuser might get
> some "force"-parameter that tells it to delete and recreate the user if it
> already exists. Thoughts?
Tell the user to do it manually in pk
Hi,
Following situation: Older mailman ebuilds used to set the mailman user home
to /usr/local/mailman (which is obviously wrong).
Now with the new mailman ebuild, various directories are configurable.
The mailman user is created with the enewuser macro. Now, the problem is that
enewuser just
