From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org
Date: Sun, 11 Aug 2019 14:48:28 -0500 [thread overview]
Message-ID: <20190811194828.GA2329@linux1.home> (raw)
In-Reply-To: <CAEdQ38FSVkPHfyU-D87Vg7+f6GdxwNcpKOLYecXmU59SnpoQTA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]
On Sat, Aug 10, 2019 at 05:41:56PM -0700, Matt Turner wrote:
> On Sat, Aug 10, 2019 at 1:49 PM William Hubbs <williamh@gentoo.org> 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
>
> That's true, but I think with editor settings embedded in the file and
> visual pattern of vertical alignment we shouldn't expect a bunch of
> problems.
We don't honor editor settings in files by default, so this will not
work out of the box (see this in /etc/vim/vimrc).
--- cut here ---
" {{{ Modeline settings
" We don't allow modelines by default. See bug #14088 and bug #73715.
" If you're not concerned about these, you can enable them on a per-user
" basis by adding "set modeline" to your ~/.vimrc file.
set nomodeline
" }}}
--- cut here ---
If we are going to require a modeline, shouldn't we consider allowing
them by default so we can work out of the box instead of having to tweak
our editor settings?
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-08-11 19:48 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
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 [this message]
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=20190811194828.GA2329@linux1.home \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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