public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] GLEP 55 Version 2
Date: Sat, 06 Jun 2009 23:31:47 +0100	[thread overview]
Message-ID: <1244327519.3832.1@NeddySeagoon> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ladies and Gentlemen,

I've spent some time reading all of this years emails on GLEP55 and 
added a few lines to version 1.5 which is the last offical version.

The HTML version (not with the GLEP style sheet) is at 
http://xrl.us/bevrnb (my devspace)
Its not ready to go to council as it still needs additional content 
which I don't have the background to contribuite. My role in this 
version of GLEP 55 has been interpretation and editorial.

I'm looking for three elements to add.

1. A description of the steps the PM needs to extract the EAPI in 
ebuilds today, if its any more than sourcing the ebuild.

2. Benchmarks and supporting code for EAPI extraction for EAPI in the 
filename.

3. Benchmarks and supporting code for EAPI extraction for EAPI in the 
ebuild.

Benchmarks for valid and invalid cache need to be supplied so we have 
both the user and developer views of performace. 

I expect items 2 and 3 to be provided by the proponents of these two 
competing options and critically examined for validity by the 
competitors.

When the above data is available, I'll update the document as it needs 
to contain all of the evidence to allow council to reach a decision 
without reading the ml. 

Reply with corrections and factual additions with supporting evidence 
only please. The role of the GLEP is to present the evidence and make a 
reccomendation. Its councils job to make any subjective assessments 
having read the GLEP.

- -- 
Regards,

Roy Bamford
(NeddySeagoon) a member of
gentoo-ops
forum-mods
treecleaners
trustees
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkoq7l8ACgkQTE4/y7nJvatqjQCeNe/mqS8goPZ5+H4yftn19mYJ
5i0AoLwsAmKcc6Ux4zjG3dExgRbcltwl
=edR+
-----END PGP SIGNATURE-----




             reply	other threads:[~2009-06-06 22:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-06 22:31 Roy Bamford [this message]
2009-06-07  3:32 ` [gentoo-dev] Re: GLEP 55 Version 2 Steven J Long
2009-06-07  9:34   ` Ulrich Mueller
2009-06-07 11:55     ` Richard Freeman
2009-06-07 13:16       ` Duncan
2009-06-07 12:15     ` Patrick Lauer
2009-06-07 13:27       ` Richard Freeman
2009-06-07 12:40     ` Federico Ferri
2009-06-07 14:11     ` Roy Bamford
2009-06-08 12:42       ` [gentoo-dev] " Steven J Long
2009-06-08 10:18 ` [gentoo-dev] " Michael Haubenwallner
     [not found] <20090607163041.09a1452e@anaconda.krait.us>
2009-06-08 15:48 ` Ferris McCormick
2009-06-08 20:24   ` [gentoo-dev] " Roy Bamford

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=1244327519.3832.1@NeddySeagoon \
    --to=neddyseagoon@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