public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: allow -1 for ACCT_USER_ID and ACCT_GROUP_ID in ::gentoo
Date: Sun, 28 Nov 2021 18:26:59 -0500	[thread overview]
Message-ID: <4accff715fedc3c142bdb67e4b52cfc0cfd6bb4a.camel@gentoo.org> (raw)
In-Reply-To: <YaQDMJAFrbAEiJeC@linux1.home>

On Sun, 2021-11-28 at 16:31 -0600, William Hubbs wrote:
> All,
> 
> I want to discuss why we ban -1 as the ACCT_USER_ID and ACCT_GROUP_ID setting
> for all acct-user and acct-group packages in ::gentoo.
> 
> Here are my thoughts about it.
> 
> - As Gordon pointed out, it isn't necessary for us to care about UIDS/GIDS
>   most of the time.

It's not for you. It's for end users. And you don't have to care about
them. Just pick any old number.


> - I realize that our settings are suggestions, but the values we can
>   suggest are not infinite. We have run out once, and it is only a matter of
>   time until we do again.

We did not run out. The council placed an arbitrary limit on them once,
and then had to raise their own arbitrary limit.

Nobody complaining about "running out" understands what the GLEP says.
If we ever hit 2^16 acct-group packages, feel free to reuse them, or
keep counting. Nothing bad will happen. The worst case scenario is
still better than if no hint was given at all.


> - If an end user needs to care about the UID/GID, they can easily override
>   the settings in make.conf.

The point of the feature is to encourage all new installs to have
consistent UIDs/GIDs by default, without user intervention. Your
suggestion does not solve the same problem, and requires more work to
not solve it.


> 
> Thoughts? In particular, I want to hear from folks who disagree with me
> about using -1 in the main tree for most packages.
> 

The only problem that anyone has put forth is one that does not exist.
UIDs and GIDs are still assigned dynamically in Gentoo. The number you
type in the ebuild is only a hint: it's the first number that will be
tried during the dynamic assignment. There is no limit on the number of
hints, and we will never run out because a conflict is never possible,
because the damned things are assigned dynamically.

Is there an actual problem?




  reply	other threads:[~2021-11-28 23:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 22:31 [gentoo-dev] rfc: allow -1 for ACCT_USER_ID and ACCT_GROUP_ID in ::gentoo William Hubbs
2021-11-28 23:26 ` Michael Orlitzky [this message]
2021-11-28 23:39   ` Sam James
2021-11-29  0:06     ` Michael Orlitzky
2021-11-29  5:05       ` Sam James
2021-11-29 13:25         ` Michael Orlitzky
2021-11-29  4:07 ` Michał Górny
2021-11-29  6:58   ` Alec Warner
2021-11-29 10:24     ` Ulrich Mueller
2021-11-30  0:49       ` James Cloos
2021-11-30 11:59         ` Ulrich Mueller
2021-11-30 21:08           ` James Cloos
2021-12-01  1:32           ` William Hubbs
2021-12-01  1:42             ` Michael Orlitzky
2021-12-01  6:16             ` Jaco Kroon
2021-12-01  6:45               ` Alec Warner
2021-12-01  7:51                 ` Jaco Kroon
2021-12-01 12:22                 ` Michael Orlitzky
2021-12-01 16:52             ` A Schenck
2021-11-30  0:55       ` Alec Warner

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=4accff715fedc3c142bdb67e4b52cfc0cfd6bb4a.camel@gentoo.org \
    --to=mjo@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