From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id CE4F9138334 for ; Sat, 10 Aug 2019 22:53:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 15A3EE086A; Sat, 10 Aug 2019 22:53:47 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B1B78E085E for ; Sat, 10 Aug 2019 22:53:46 +0000 (UTC) Received: from linux1.home (cpe-66-68-48-101.austin.res.rr.com [66.68.48.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: williamh) by smtp.gentoo.org (Postfix) with ESMTPSA id 74626349895; Sat, 10 Aug 2019 22:53:45 +0000 (UTC) Received: (nullmailer pid 3097 invoked by uid 1000); Sat, 10 Aug 2019 22:53:43 -0000 Date: Sat, 10 Aug 2019 17:53:43 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Cc: ulm@gentoo.org, mgorny@gentoo.org Subject: Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org Message-ID: <20190810225343.GB2735@linux1.home> Mail-Followup-To: gentoo-dev@lists.gentoo.org, ulm@gentoo.org, mgorny@gentoo.org References: <87a7f00e6badd6e0c4247aa8853c4934bbae092e.camel@gentoo.org> <20190810204917.GA2657@linux1.home> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Archives-Salt: 7d5f4cc1-d0d2-4f89-9af1-c11cd2856c5e X-Archives-Hash: 50b272420cd83b6a9fd9b5371c3718ce --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 11, 2019 at 12:40:04AM +0200, Ulrich Mueller wrote: > >>>>> On Sat, 10 Aug 2019, William Hubbs wrote: > =20 > > I propose using a colon like we do in /etc/passwd: >=20 > > root:0:0:baselayout: > > bin:1:1:baselayout:some notes go here >=20 > Please no. I thought the purpose of this exercise was to have a format > that is human readable, and not something with strange separators like > ":" or "|" (as we have in the wiki)? >=20 > There cannot be any whitespace in name, IDs, or provider. > So what would be the problem with using whitespace as separators? Well, I suppose it wouldn't be a problem if we don't care about alignment, but that is not readable either really right? For example, (completely making up uid/gid numbers), this is totally valid. root 0 0 baselayout this is from baselayout bin 1 1 baselayout this is from baselayout postgresql 150 150 app this is from postgresql cockroach 250 250 app this is from cockroach William --3uo+9/B/ebqu+fSQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCXU9K9wAKCRBuVBb0MMRl OJMJAJ0ZuSQXHea9UQtoCYQUPeUJ9BGHGwCgqKhK+I53mUq19x/sNO3jMW+SBgs= =jbCk -----END PGP SIGNATURE----- --3uo+9/B/ebqu+fSQ--