From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2 6/9] acct-{group,user}.eclass: WIP eclasses to maintain users/groups
Date: Thu, 06 Jun 2019 09:05:32 +0200 [thread overview]
Message-ID: <w6g4l538a83.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <009f8dcb15523a2cef659cbb3d9b31ca251ba69a.camel@gentoo.org> ("Michał Górny"'s message of "Thu, 06 Jun 2019 06:57:20 +0200")
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
>>>>> On Thu, 06 Jun 2019, Michał Górny wrote:
> On Wed, 2019-06-05 at 21:10 +0200, Pacho Ramos wrote:
>> > +# Then you add appropriate dependency to your package. The dependency
>> > +# type(s) should be:
>> > +# - DEPEND (+ RDEPEND) if the group is already needed at build time,
>> > +# - RDEPEND if it is needed at install time (e.g. you 'fowners' files
>> > +# in pkg_preinst),
>> > +# - PDEPEND if it is only needed at runtime.
>>
>> Maybe is a stupid question but, why is PDEPEND preferred over RDEPEND
>> for packages needing the group only at runtime?
> To delay user creation as far as possible, in case the package failed
> to build. Not that it will usually work since Portage will install
> the user early anyway.
It isn't very useful then, and is more error prone than having RDEPEND
in both the second and third case. Plus, errors won't be necessarily
caught, because Portage will treat PDEPEND in the same way as RDEPEND
(unless there would be circular dependencies, but I don't see how that
could happen).
So, simplify and go for RDEPEND (+DEPEND if needed) only?
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-06-06 7:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 9:12 [gentoo-dev] [PATCH v2 0/9] User/group packages Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 1/9] user.eclass: Do not create user-group automatically Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 2/9] user.eclass: Prevent automated home creation in useradd Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 3/9] user.eclass: Support disabling home directory creation Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 4/9] user.eclass: Support forcing specified UID/GID Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 5/9] user.eclass: Die if no free UID/GID is found Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 6/9] acct-{group,user}.eclass: WIP eclasses to maintain users/groups Michał Górny
2019-06-05 11:46 ` Ulrich Mueller
2019-06-06 4:56 ` Michał Górny
2019-06-05 19:10 ` Pacho Ramos
2019-06-06 4:57 ` Michał Górny
2019-06-06 7:05 ` Ulrich Mueller [this message]
2019-06-05 21:14 ` Michael Orlitzky
2019-06-06 5:02 ` Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 7/9] acct-group/ftp: Add 'ftp' group (GID 21) Michał Górny
[not found] ` <3868289f-1e37-631a-daeb-d1a4b2454669@gentoo.org>
2019-06-07 5:01 ` Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 8/9] acct-user/ftp: Add 'ftp' user (UID 21) Michał Górny
2019-06-05 9:12 ` [gentoo-dev] [PATCH v2 9/9] net-ftp/ftpbase: Utilize {group,user}/ftp Michał Górny
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=w6g4l538a83.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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