| 1 |
On Sat, 2019-08-10 at 15:49 -0500, William Hubbs wrote: |
| 2 |
> On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote: |
| 3 |
> > Hi, |
| 4 |
> > |
| 5 |
> > Some time ago William asked me to move UID/GID assignments from wiki [1] |
| 6 |
> > to something more accessible. I've finally gotten around to draft |
| 7 |
> > something, and I'd like to hear your comments about it. The idea is to |
| 8 |
> > keep a whitespace-separated record format file in api.gentoo.org repo. |
| 9 |
> > |
| 10 |
> > This is mostly inspired by Fedora's format, specifically the ability to |
| 11 |
> > specify both UID and GID for matching user/group on the same line. |
| 12 |
> > I've also decided not to attempt to specify disjoint Linux and FreeBSD |
| 13 |
> > users/groups on a single line. Instead, they are specified separately |
| 14 |
> > and defined by providers (as suggested by Ulrich). |
| 15 |
> > |
| 16 |
> > Sample, along with big comment explaining the file format, below. |
| 17 |
> |
| 18 |
> I'm not sure how I feel about whitespace delimiters for this. withno |
| 19 |
> further specification, it would make these two lines completely valid: |
| 20 |
> |
| 21 |
> root 0 0 baselayout |
| 22 |
> bin 1 1 baselayout some notes here |
| 23 |
> |
| 24 |
> I propose using a colon like we do in /etc/passwd: |
| 25 |
> |
| 26 |
> root:0:0:baselayout: |
| 27 |
> bin:1:1:baselayout:some notes go here |
| 28 |
> |
| 29 |
> Thoughts? |
| 30 |
> |
| 31 |
|
| 32 |
Worksforme. Do we allow extra whitespace in fields where it doesn't |
| 33 |
matter for alignment? |
| 34 |
|
| 35 |
-- |
| 36 |
Best regards, |
| 37 |
Michał Górny |
Archives