public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 27 Bump
Date: Sun, 15 Nov 2009 22:50:44 -0600	[thread overview]
Message-ID: <eafa4c130911152050k7ab1d598g8d9a9d247af6e4fc@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20091116T013243-490747904Z@orbis-terrarum.net>

On Sun, Nov 15, 2009 at 7:35 PM, Robin H. Johnson <robbat2@gentoo.org> wrote:
> On Sun, Nov 15, 2009 at 09:25:45AM +0200, Petteri Räty wrote:
>> Doug Goldstein wrote:
>> > GLEP 27 [1] seems pretty stagnant and I'm planning on giving it a bit
>> > of a refresh and actually implementing it. Now before I do this I'm
>> > not in love with the format in tree but I haven't decided on a format
>> > exactly in my head. So that being said, I'm sending this out looking
>> > for some opinions or ideas for my new GLEP. One of the obvious things
>> > I'll cover is all the ambiguity of the GLEP with regard to the data
>> > inside each of the files.
>> >
>> > [1] http://www.gentoo.org/proj/en/glep/glep-0027.html
>> One idea worth considering is making users just ebuilds with a
>> supporting eclass.
> While I'm hugely in favour of having consistent UID/GIDs with no
> conflicts over all Gentoo machines, I feel one of the reasons that the
> GLEP failed was that users required by ebuilds changed over ebuild
> versions, and the GLEP didn't seem to handle that well.
>
> Cases I've seen in the tree:
> - username change (slocate -> locate)
> - homedir change
> - shell change
>

Which would seem to mean that Petteri's suggestion would work better
since that would allow us to version/upgrade user/group data.



-- 
Doug Goldstein



      reply	other threads:[~2009-11-16  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15  4:37 [gentoo-dev] GLEP 27 Bump Doug Goldstein
2009-11-15  7:25 ` Petteri Räty
2009-11-16  1:35   ` Robin H. Johnson
2009-11-16  4:50     ` Doug Goldstein [this message]

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=eafa4c130911152050k7ab1d598g8d9a9d247af6e4fc@mail.gmail.com \
    --to=cardoe@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