-----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-----
