public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New acct-* package policy
Date: Mon, 6 Jan 2020 09:39:59 +0200	[thread overview]
Message-ID: <be28132b-1462-7ea7-4ff0-612e63872697@gentoo.org> (raw)
In-Reply-To: <a4625acb-b270-f328-795d-ecde7415d74b@gmx.net>


[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]


On 1/6/20 2:36 AM, Martin Dummer wrote:
> Am 21.12.19 um 18:32 schrieb Michał Górny:
>> Please commit and push uid-gid.txt [3] change to data/api.git *before*
>> your packages.  This makes sure that any potential collisions are caught
>> as merge conflicts before they hit users.  The CI also catches UID/GID
>> collisions.
>
>
> pull requests.
>
> So for proxy-maintained packages which need acct-user/acct-group ebuilds
> this must be
>
> - either done like before - announcement on the gentoo-dev ML, then
> committed by ???
>
> - or done by a member of the proxy-maintainers group.

- your package will be assigned the next free ID by whoever commits.
(your 2nd option)

From the end-user point it doesn't matter much whether it's 321 or 320
as long as it stays the same after being merged. Although I'm still of
the opinion we should try to **pick** same IDs that other distros use,
but it's already looking desperate for that matter.

But if you have time, please do make a pull request to URL mentioned by
Ralph and Aaron.


>
> Maybe you find the time to refine that exception in the documentation.

I think having some guidance on proxy-maint project wiki page about this
whole acct- thing wouldn't hurt, but it may come a bit too late already.


-- juippis



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]

      parent reply	other threads:[~2020-01-06  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21 17:32 [gentoo-dev] New acct-* package policy Michał Górny
2020-01-06  0:36 ` Martin Dummer
2020-01-06  0:41   ` Ralph Seichter
2020-01-06  0:46   ` Aaron Bauman
2020-01-06  7:39   ` Joonas Niilola [this message]

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=be28132b-1462-7ea7-4ff0-612e63872697@gentoo.org \
    --to=juippis@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