public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 0/6] nix and guix GID/UID assignments
Date: Mon, 25 Nov 2019 20:28:10 +0000	[thread overview]
Message-ID: <20191125202810.0bbecdf5@sf> (raw)
In-Reply-To: <139dd6ae99d13ddf68aac96c65120d9870620ef0.camel@gentoo.org>

On Mon, 25 Nov 2019 17:24:08 +0100
David Seifert <soap@gentoo.org> wrote:

> On Sun, 2019-11-24 at 20:35 +0000, Sergei Trofimovich wrote:
> > On Sun, 24 Nov 2019 17:19:36 +0100
> > Ulrich Mueller <ulm@gentoo.org> wrote:
> >   
> > > > > > > > On Sun, 24 Nov 2019, Sergei Trofimovich wrote:    
> > > > I interpreted 'reserved' as 'free to use' on
> > > >     
> > > > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/UID_GID_Assignment
> > > > Can you tweak it to someting other than 'reserved' so it would be
> > > > clear?    
> > > 
> > > That's what the "Notes" column was intended for.
> > >   
> > > > I'll use 60001 .. 60999 / 61001 .. 61999. Is it free though?
> > > > '60001..65533' claims to also be 'reserved' as well.    
> > > 
> > > Debian is also using the range above 60000 for allocations that
> > > won't
> > > fit into the low range. Theoretically, there is some overlap with
> > > systemd dynamic users (61184..65519), but IIUC assigning other UIDs
> > > in
> > > that range isn't a problem, as long as there are enough free IDs
> > > left.
> > > 
> > > Another question, the above are about 2000 users and 2000 groups.
> > > Does that imply that we will eventually end up with 4000 packages
> > > in acct-{user,group}?  
> > 
> > Should be 2000 users, 2 groups. Worst case it's 2002 packages, yes.
> >   
> 
> For a package manager that likely only 3 Gentoo users in the world use?

I'll avoid debating you scientific method of deriving that number.
What is your threshold? 10 users? 1000 users? 100000 users?

> I don't consider that particularly helpful, and am very much inclined
> to oppose that.

I'm fine with current use of user.eclass if QA grants nix and guix an
exception to use user.eclass indefinitely instead of GLEP-81 layout.

-- 

  Sergei


  reply	other threads:[~2019-11-25 20:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 12:46 [gentoo-dev] [PATCH 0/6] nix and guix GID/UID assignments Sergei Trofimovich
2019-11-24 12:46 ` [gentoo-dev] [PATCH 1/6] acct-group/nixbld: new group (GID 30000) Sergei Trofimovich
2019-11-24 12:46 ` [gentoo-dev] [PATCH 2/6] acct-group/guixbuild: new group (GID 31000) Sergei Trofimovich
2019-11-24 12:46 ` [gentoo-dev] [PATCH 3/6] acct-user/nixbld{1..10}: new user (UID {30001..30010) Sergei Trofimovich
2019-11-24 12:46 ` [gentoo-dev] [PATCH 4/6] acct-user/guixbuilder{1..10}: new user (UID {31001..31010) Sergei Trofimovich
2019-11-24 12:46 ` [gentoo-dev] [PATCH 5/6] sys-apps/nix: switch from user.eclass to acct-*/ depends Sergei Trofimovich
2019-11-24 12:46 ` [gentoo-dev] [PATCH 6/6] sys-apps/guix: " Sergei Trofimovich
2019-11-24 12:57 ` [gentoo-dev] [PATCH 0/6] nix and guix GID/UID assignments Ulrich Mueller
2019-11-24 13:23   ` Sergei Trofimovich
2019-11-24 16:19     ` Ulrich Mueller
2019-11-24 20:35       ` Sergei Trofimovich
2019-11-25 16:24         ` David Seifert
2019-11-25 20:28           ` Sergei Trofimovich [this message]
2019-11-25 20:32             ` Michał Górny
2019-11-25 20:38               ` Sergei Trofimovich

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=20191125202810.0bbecdf5@sf \
    --to=slyfox@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