public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2 6/9] acct-{group,user}.eclass: WIP eclasses to maintain users/groups
Date: Wed, 05 Jun 2019 21:10:47 +0200	[thread overview]
Message-ID: <c84b0ee058d9c3e31035e1ed4844b5d54a52703c.camel@gentoo.org> (raw)
In-Reply-To: <20190605091257.12127-7-mgorny@gentoo.org>

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

El mié, 05-06-2019 a las 11:12 +0200, Michał Górny escribió:
> [...]
> +# 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? 

If I don't misremember, PDEPEND was meant to be used to avoid circular deps
issues, while using RDEPEND otherwise

Thanks :)

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

  parent reply	other threads:[~2019-06-05 19:10 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 [this message]
2019-06-06  4:57     ` Michał Górny
2019-06-06  7:05       ` Ulrich Mueller
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=c84b0ee058d9c3e31035e1ed4844b5d54a52703c.camel@gentoo.org \
    --to=pacho@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