From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 27 Bump
Date: Sun, 15 Nov 2009 09:25:45 +0200 [thread overview]
Message-ID: <4AFFACF9.6000905@gentoo.org> (raw)
In-Reply-To: <eafa4c130911142037m2a082321k36d726b99ec3bca5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
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.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2009-11-15 8:08 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 [this message]
2009-11-16 1:35 ` Robin H. Johnson
2009-11-16 4:50 ` Doug Goldstein
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=4AFFACF9.6000905@gentoo.org \
--to=betelgeuse@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