public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org
Date: Sat, 10 Aug 2019 22:51:52 +0200	[thread overview]
Message-ID: <ed51f40244a087e02dc3b0f5c69f0c34ba2eb406.camel@gentoo.org> (raw)
In-Reply-To: <20190810204917.GA2657@linux1.home>

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

On Sat, 2019-08-10 at 15:49 -0500, William Hubbs wrote:
> On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > Hi,
> > 
> > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > to something more accessible.  I've finally gotten around to draft
> > something, and I'd like to hear your comments about it.  The idea is to
> > keep a whitespace-separated record format file in api.gentoo.org repo.
> > 
> > This is mostly inspired by Fedora's format, specifically the ability to
> > specify both UID and GID for matching user/group on the same line.
> > I've also decided not to attempt to specify disjoint Linux and FreeBSD
> > users/groups on a single line.  Instead, they are specified separately
> > and defined by providers (as suggested by Ulrich).
> > 
> > Sample, along with big comment explaining the file format, below.
> 
> I'm not sure how I feel about whitespace delimiters for this. withno
> further specification, it would make these two lines completely valid:
> 
> root 0 0 baselayout
> bin 1				1				baselayout					some notes here
>  
>  I propose using a colon like we do in /etc/passwd:
> 
>  root:0:0:baselayout:
>  bin:1:1:baselayout:some notes go here
> 
>  Thoughts?
> 

Worksforme.  Do we allow extra whitespace in fields where it doesn't
matter for alignment?

-- 
Best regards,
Michał Górny


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

  reply	other threads:[~2019-08-10 20:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 21:29 [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org Michał Górny
2019-08-10 20:49 ` William Hubbs
2019-08-10 20:51   ` Michał Górny [this message]
2019-08-10 22:44     ` William Hubbs
2019-08-10 22:40   ` Ulrich Mueller
2019-08-10 22:53     ` William Hubbs
2019-08-11  6:38       ` Ulrich Mueller
2019-08-11  0:41   ` Matt Turner
2019-08-11 19:48     ` William Hubbs
2019-08-11 22:04       ` Matt Turner
2019-08-11 22:53         ` William Hubbs
2019-08-12  0:11           ` Matt Turner
2019-08-12  2:50           ` Michał Górny
2019-08-12 16:52             ` Alec Warner
2019-08-12 17:58               ` Kent Fredric
2019-08-12 18:20                 ` Alec Warner
2019-08-12 18:33                   ` Kent Fredric
2019-08-12 19:01                   ` Kent Fredric
2019-08-12 17:42           ` Kent Fredric
2019-08-17  7:06 ` [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org (v2) Michał Górny
2019-08-17  7:38   ` Michał Górny
2019-08-18  6:23   ` Ulrich Mueller

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=ed51f40244a087e02dc3b0f5c69f0c34ba2eb406.camel@gentoo.org \
    --to=mgorny@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