Gentoo Archives: gentoo-dev

From: William Hubbs <williamh@g.o>
To: gentoo-dev@l.g.o
Cc: "Michał Górny" <mgorny@g.o>
Subject: Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org
Date: Sun, 11 Aug 2019 19:48:38
Message-Id: 20190811194828.GA2329@linux1.home
In Reply to: Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org by Matt Turner
1 On Sat, Aug 10, 2019 at 05:41:56PM -0700, Matt Turner wrote:
2 > On Sat, Aug 10, 2019 at 1:49 PM William Hubbs <williamh@g.o> wrote:
3 > >
4 > > On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
5 > > > Hi,
6 > > >
7 > > > Some time ago William asked me to move UID/GID assignments from wiki [1]
8 > > > to something more accessible. I've finally gotten around to draft
9 > > > something, and I'd like to hear your comments about it. The idea is to
10 > > > keep a whitespace-separated record format file in api.gentoo.org repo.
11 > > >
12 > > > This is mostly inspired by Fedora's format, specifically the ability to
13 > > > specify both UID and GID for matching user/group on the same line.
14 > > > I've also decided not to attempt to specify disjoint Linux and FreeBSD
15 > > > users/groups on a single line. Instead, they are specified separately
16 > > > and defined by providers (as suggested by Ulrich).
17 > > >
18 > > > Sample, along with big comment explaining the file format, below.
19 > >
20 > > I'm not sure how I feel about whitespace delimiters for this. withno
21 > > further specification, it would make these two lines completely valid:
22 > >
23 > > root 0 0 baselayout
24 > > bin 1 1 baselayout some notes here
25 >
26 > That's true, but I think with editor settings embedded in the file and
27 > visual pattern of vertical alignment we shouldn't expect a bunch of
28 > problems.
29
30 We don't honor editor settings in files by default, so this will not
31 work out of the box (see this in /etc/vim/vimrc).
32
33 --- cut here ---
34 " {{{ Modeline settings
35 " We don't allow modelines by default. See bug #14088 and bug #73715.
36 " If you're not concerned about these, you can enable them on a per-user
37 " basis by adding "set modeline" to your ~/.vimrc file.
38 set nomodeline
39 " }}}
40 --- cut here ---
41
42 If we are going to require a modeline, shouldn't we consider allowing
43 them by default so we can work out of the box instead of having to tweak
44 our editor settings?
45
46 William

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies