public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Scratching of GLEP22
Date: Fri, 7 Oct 2005 00:03:35 +0200	[thread overview]
Message-ID: <200510070003.56151@enterprise.flameeyes.is-a-geek.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

Hi all,

In the last days on gentoo-alt we discussed about the need for a 
reorganization of keywords for Gentoo/ALT projects, basically what is being 
treated by GLEP22 currently.

And it was quite unanimous that GLEP22 solution is not adapt. Having a 4-part 
keyword is not going to help anything. The new ${ELIBC} ${KERNEL} and 
${USERLAND} supersedes that; also we're going to make them automatically 
loaded from $CHOST/$CBUILD. The new keywords are being simplified to a simple 
2-part keywords like they are used now (x86-fbsd ppc-macos ...).

For this reason I'd like to ask the retirement by scratch of GLEP22.. hope 
you'll let me do that without having to write a GLEP that removes a GLEP 
(it's recursive...)

Thanks,
-- 
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-10-06 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 22:03 Diego 'Flameeyes' Pettenò [this message]
2005-10-07 12:25 ` [gentoo-dev] Scratching of GLEP22 Chris Gianelloni
2005-10-13 18:37   ` Diego 'Flameeyes' Pettenò
2005-10-13 19:20     ` Grant Goodyear

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=200510070003.56151@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@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