public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: acct-user/... modifies existing user sometimes
Date: Sat, 14 Dec 2019 22:16:58 +0100	[thread overview]
Message-ID: <51af6b01483030c625bf805d4b4f3b8175dd6790.camel@gentoo.org> (raw)
In-Reply-To: <51d34968-f80e-1fb8-462c-460785a862e2@earthlink.net>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

On Sat, 2019-12-14 at 14:47 -0600, The Bit Pit wrote:
> acct-user/mythtv modifies the existing user if that user is not logged 
> in. Mythtv has been around for years and users have created specialized 
> configurations for the mythtv user. They do not like changes to the 
> mythtv user when upgrading.
> 
> A couple of solutions:
> 
> 1)
> the ebuild does not depend on acct-user/mythtv when the user already 
> exists. This prevents both the changing and deletion of the existing user.
> 
> What is the gentoo way to discover a preexisting user? Repoman does not 
> like anything I tried using egetent passwd mythtv
> 
> 2)  Add something to the acct-user/mythtv to (conditionally) prevent any 
> change if there is a preexisting user on the system. The acct-user 
> unmerge would also check that the user was not modified since it was 
> created by acct-user. This seems like a lot of work.
> 

Users are supposed to create a local acct-user/mythtv override if they
want to use a custom setup.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2019-12-14 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 20:47 [gentoo-dev] RFC: acct-user/... modifies existing user sometimes The Bit Pit
2019-12-14 21:16 ` Michał Górny [this message]
2019-12-14 22:02 ` Thomas Deutschmann
2019-12-15 23:31   ` Michael Orlitzky
2019-12-16 20:43     ` The Bit Pit

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=51af6b01483030c625bf805d4b4f3b8175dd6790.camel@gentoo.org \
    --to=mgorny@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