public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Use GLEP27!
Date: Tue, 15 Dec 2015 15:56:34 +0100	[thread overview]
Message-ID: <22128.10786.56727.199802@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20151215141936.GQ11489@vapier.lan>

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

>>>>> On Tue, 15 Dec 2015, Mike Frysinger wrote:

> a flat text file akin to /etc/passwd is not readable.  xml is readable.

ESR's case study about the password file format seems to disagree:
http://www.catb.org/esr/writings/taoup/html/ch05s01.html#id2901332

I think the name:password:uid:gid:gecos:directory:shell format is
readable well enough for human eyes. Certainly it is machine readable;
even with standard tools like fgetpwent(3) (or its equivalent in other
programming languages).

> a markdown like format would work -- easy to parse by machines & humans
> and is a single stackable file.

Reinventing the wheel?

> user:ntp
> <whitespace>uid:203
> <whitespace>gid:203
> user:man
> <whitespace>uid:13
> <whitespace>gid:13
> (using : as delimiter since that's what *NIX uses in /etc/passwd)

> the main one would grow probably to about 2000+ lines (~400 users in
> the tree and each entry takes ~4 lines assuming we enforce eliding
> of defaults) which isn't that terrible.

To me this looks like a lot of added redundancy for little (if any)
benefit.

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2015-12-15 14:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 18:03 [gentoo-dev] Determenistic system group and user id Alexey Shvetsov
2015-12-13 20:41 ` [gentoo-dev] Use GLEP27! Robin H. Johnson
2015-12-14  4:49   ` Alexey Shvetsov
2015-12-14  6:06     ` Robin H. Johnson
2015-12-14 14:48       ` Doug Goldstein
2015-12-14  9:22   ` Michał Górny
2015-12-14 14:57     ` Doug Goldstein
2015-12-14 20:22     ` Ulrich Mueller
2015-12-15  4:00       ` Peter Stuge
2015-12-15  5:13       ` Mike Frysinger
2015-12-15  6:28         ` Ulrich Mueller
2015-12-15 14:19           ` Mike Frysinger
2015-12-15 14:33             ` Michał Górny
2015-12-15 15:08               ` Mike Frysinger
2015-12-15 15:24                 ` Anthony G. Basile
2015-12-15 19:17                   ` Mike Frysinger
2015-12-15 14:56             ` Ulrich Mueller [this message]
2015-12-15 15:00               ` Michał Górny
2015-12-15 15:10                 ` Mike Frysinger
2015-12-15 15:16               ` Mike Frysinger
2015-12-15 20:52               ` Mike Frysinger
2015-12-15 21:35                 ` Ulrich Mueller
2015-12-15 21:55                   ` Mike Frysinger
2015-12-16  1:23                     ` Anthony G. Basile
2015-12-16  4:04                       ` Mike Frysinger
2015-12-17 10:57                         ` Ulrich Mueller
2015-12-17 13:45                           ` Mike Frysinger
2015-12-15 18:35             ` Alec Warner
2015-12-15 19:22               ` Mike Frysinger
2015-12-13 20:58 ` [gentoo-dev] Determenistic system group and user id Mike Gilbert
2015-12-13 22:23 ` Alec Warner
2015-12-13 23:46   ` Marc Schiffbauer
2015-12-14  5:17   ` Alexey Shvetsov
2015-12-14  6:39   ` Robin H. Johnson
2015-12-14 20:03     ` 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=22128.10786.56727.199802@a1i15.kph.uni-mainz.de \
    --to=ulm@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