From: "Ulrich Mueller (ulm)" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/glep: glep-0055.html glep-0055.txt gleps.xml
Date: Wed, 9 May 2012 19:37:01 +0000 (UTC) [thread overview]
Message-ID: <20120509193701.B3C7C2004B@flycatcher.gentoo.org> (raw)
ulm 12/05/09 19:37:01
Modified: glep-0055.html glep-0055.txt gleps.xml
Log:
Update status of GLEP 55 according to council decision on 2012-05-08.
Revision Changes Path
1.7 xml/htdocs/proj/en/glep/glep-0055.html
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0055.html?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0055.html?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0055.html?r1=1.6&r2=1.7
Index: glep-0055.html
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0055.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- glep-0055.html 7 Apr 2010 22:12:52 -0000 1.6
+++ glep-0055.html 9 May 2012 19:37:01 -0000 1.7
@@ -4,7 +4,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />
+ <meta name="generator" content="Docutils 0.8.1: http://docutils.sourceforge.net/" />
<title>GLEP 55 -- Use EAPI-suffixed ebuilds (.ebuild-EAPI)</title>
<link rel="stylesheet" href="tools/glep.css" type="text/css" /></head>
<body bgcolor="white">
@@ -33,7 +33,7 @@
</tr>
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Piotr Jaroszyński <peper at gentoo.org></td>
</tr>
-<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
+<tr class="field"><th class="field-name">Status:</th><td class="field-body">Rejected</td>
</tr>
<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
</tr>
@@ -49,28 +49,29 @@
<div class="contents topic" id="contents">
<p class="topic-title first">Contents</p>
<ul class="simple">
-<li><a class="reference internal" href="#abstract" id="id3">Abstract</a></li>
-<li><a class="reference internal" href="#problem" id="id4">Problem</a></li>
-<li><a class="reference internal" href="#current-behaviour" id="id5">Current behaviour</a><ul>
-<li><a class="reference internal" href="#incompatible-change-of-inherit-e-g-make-it-look-in-the-package-dir-too" id="id6">Incompatible change of inherit (e.g. make it look in the package dir too)</a></li>
-<li><a class="reference internal" href="#new-global-scope-function" id="id7">New global scope function</a></li>
-<li><a class="reference internal" href="#new-version-format" id="id8">New version format</a></li>
-<li><a class="reference internal" href="#use-newer-bash-features" id="id9">Use newer bash features</a></li>
+<li><a class="reference internal" href="#status" id="id3">Status</a></li>
+<li><a class="reference internal" href="#abstract" id="id4">Abstract</a></li>
+<li><a class="reference internal" href="#problem" id="id5">Problem</a></li>
+<li><a class="reference internal" href="#current-behaviour" id="id6">Current behaviour</a><ul>
+<li><a class="reference internal" href="#incompatible-change-of-inherit-e-g-make-it-look-in-the-package-dir-too" id="id7">Incompatible change of inherit (e.g. make it look in the package dir too)</a></li>
+<li><a class="reference internal" href="#new-global-scope-function" id="id8">New global scope function</a></li>
+<li><a class="reference internal" href="#new-version-format" id="id9">New version format</a></li>
+<li><a class="reference internal" href="#use-newer-bash-features" id="id10">Use newer bash features</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#abstract-solution" id="id10">Abstract solution</a></li>
-<li><a class="reference internal" href="#proposed-solution" id="id11">Proposed solution</a></li>
-<li><a class="reference internal" href="#specification" id="id12">Specification</a></li>
-<li><a class="reference internal" href="#summary-of-ideas" id="id13">Summary of ideas</a><ul>
-<li><a class="reference internal" href="#eapi-suffixed-ebuilds-proposed-solution" id="id14">EAPI-suffixed ebuilds (proposed solution)</a></li>
-<li><a class="reference internal" href="#eapi-in-the-filename-with-one-time-extension-change" id="id15">EAPI in the filename with one-time extension change</a></li>
-<li><a class="reference internal" href="#easily-fetchable-eapi-inside-the-ebuild" id="id16">Easily fetchable EAPI inside the ebuild</a></li>
-<li><a class="reference internal" href="#easily-fetchable-eapi-inside-the-ebuild-and-one-time-extension-change" id="id17">Easily fetchable EAPI inside the ebuild and one-time extension change</a></li>
-<li><a class="reference internal" href="#use-different-subdirectories-for-different-eapis-i-e-cat-pkg-eapix" id="id18">Use different subdirectories for different EAPIs, i.e. cat/pkg/eapiX/</a></li>
+<li><a class="reference internal" href="#abstract-solution" id="id11">Abstract solution</a></li>
+<li><a class="reference internal" href="#proposed-solution" id="id12">Proposed solution</a></li>
+<li><a class="reference internal" href="#specification" id="id13">Specification</a></li>
+<li><a class="reference internal" href="#summary-of-ideas" id="id14">Summary of ideas</a><ul>
+<li><a class="reference internal" href="#eapi-suffixed-ebuilds-proposed-solution" id="id15">EAPI-suffixed ebuilds (proposed solution)</a></li>
+<li><a class="reference internal" href="#eapi-in-the-filename-with-one-time-extension-change" id="id16">EAPI in the filename with one-time extension change</a></li>
+<li><a class="reference internal" href="#easily-fetchable-eapi-inside-the-ebuild" id="id17">Easily fetchable EAPI inside the ebuild</a></li>
+<li><a class="reference internal" href="#easily-fetchable-eapi-inside-the-ebuild-and-one-time-extension-change" id="id18">Easily fetchable EAPI inside the ebuild and one-time extension change</a></li>
+<li><a class="reference internal" href="#use-different-subdirectories-for-different-eapis-i-e-cat-pkg-eapix" id="id19">Use different subdirectories for different EAPIs, i.e. cat/pkg/eapiX/</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#references" id="id19">References</a></li>
-<li><a class="reference internal" href="#copyright" id="id20">Copyright</a></li>
+<li><a class="reference internal" href="#references" id="id20">References</a></li>
+<li><a class="reference internal" href="#copyright" id="id21">Copyright</a></li>
</ul>
</div>
<blockquote>
@@ -79,13 +80,19 @@
sobers us again."</p>
<p class="attribution">—Alexander Pope, An Essay on Criticism</p>
</blockquote>
+<div class="section" id="status">
+<h1><a class="toc-backref" href="#id3">Status</a></h1>
+<p>This GLEP was voted down by the Council in its meeting on 2010-08-23.
+The Council rejected it again in its meeting on 2012-05-08, in favour
+of parsing the EAPI from the bash assignment statement in ebuilds.</p>
+</div>
<div class="section" id="abstract">
-<h1><a class="toc-backref" href="#id3">Abstract</a></h1>
+<h1><a class="toc-backref" href="#id4">Abstract</a></h1>
<p>This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds (for
example, foo-1.2.3.ebuild-1).</p>
</div>
<div class="section" id="problem">
-<h1><a class="toc-backref" href="#id4">Problem</a></h1>
+<h1><a class="toc-backref" href="#id5">Problem</a></h1>
<p>The current way of specifying the EAPI in ebuilds is flawed. In order to get the
EAPI the package manager needs to source the ebuild, which itself needs the EAPI
in the first place. Otherwise it imposes a serious limitation, namely every ebuild,
@@ -104,11 +111,11 @@
</blockquote>
</div>
<div class="section" id="current-behaviour">
-<h1><a class="toc-backref" href="#id5">Current behaviour</a></h1>
+<h1><a class="toc-backref" href="#id6">Current behaviour</a></h1>
<p>Following subsections show what happens if you introduce any of the mentioned
changes in an ebuild and try to install it with portage 2.1.6.13.</p>
<div class="section" id="incompatible-change-of-inherit-e-g-make-it-look-in-the-package-dir-too">
-<h2><a class="toc-backref" href="#id6">Incompatible change of inherit (e.g. make it look in the package dir too)</a></h2>
+<h2><a class="toc-backref" href="#id7">Incompatible change of inherit (e.g. make it look in the package dir too)</a></h2>
<p><tt class="docutils literal"><span class="pre">sys-apps/foo-1.ebuild</span></tt>:</p>
<pre class="literal-block">
EAPI="5"
@@ -146,7 +153,7 @@
- might be pretty confusing to users.</p>
</div>
<div class="section" id="new-global-scope-function">
-<h2><a class="toc-backref" href="#id7">New global scope function</a></h2>
+<h2><a class="toc-backref" href="#id8">New global scope function</a></h2>
<p><tt class="docutils literal"><span class="pre">sys-apps/foo-1.ebuild</span></tt>:</p>
<pre class="literal-block">
EAPI="5"
@@ -171,7 +178,7 @@
<p>Not that bad as user is advised to upgrade portage.</p>
</div>
<div class="section" id="new-version-format">
-<h2><a class="toc-backref" href="#id8">New version format</a></h2>
+<h2><a class="toc-backref" href="#id9">New version format</a></h2>
<p><tt class="docutils literal"><span class="pre">sys-apps/foo-2-rc1.ebuild</span></tt>:</p>
<pre class="literal-block">
Invalid ebuild name: /var/lib/gentoo/repositories/peper/sys-apps/foo/foo-2-rc1.ebuild
@@ -181,7 +188,7 @@
<p>Not the best error message, especially if there are lots of them.</p>
</div>
<div class="section" id="use-newer-bash-features">
-<h2><a class="toc-backref" href="#id9">Use newer bash features</a></h2>
+<h2><a class="toc-backref" href="#id10">Use newer bash features</a></h2>
<p><tt class="docutils literal">|&</tt> is a new type of redirection added in bash-4. It cannot be used even in
local scope as bash still parses the whole ebuild.</p>
<p><tt class="docutils literal"><span class="pre">sys-apps/foo-1.ebuild</span></tt>:</p>
@@ -218,7 +225,7 @@
</div>
</div>
<div class="section" id="abstract-solution">
-<h1><a class="toc-backref" href="#id10">Abstract solution</a></h1>
+<h1><a class="toc-backref" href="#id11">Abstract solution</a></h1>
<p>A solution to this problem has to lift those limitations and the only way to do
it is to make the EAPI of an ebuild available to the package managers in a way
that doesn't require them to source the ebuild. Another important requirement is
@@ -228,7 +235,7 @@
issues listed on the common portage problems page - <a class="footnote-reference" href="#portageproblems" id="id2">[2]</a> - show.</p>
</div>
<div class="section" id="proposed-solution">
-<h1><a class="toc-backref" href="#id11">Proposed solution</a></h1>
+<h1><a class="toc-backref" href="#id12">Proposed solution</a></h1>
<p>The proposed solution is to use EAPI-suffixed file extensions for ebuilds. This
allows package managers to trivially read the EAPI from the ebuild filename. It
is also backwards compatible, because currently ebuilds are recognised by the
@@ -236,7 +243,7 @@
the package managers.</p>
</div>
<div class="section" id="specification">
-<h1><a class="toc-backref" href="#id12">Specification</a></h1>
+<h1><a class="toc-backref" href="#id13">Specification</a></h1>
<p>Ebuild filename extension syntax: <tt class="docutils literal"><span class="pre">ebuild[-<EAPI>]</span></tt>, where <tt class="docutils literal">[]</tt> denotes an
optional part, and <tt class="docutils literal"><EAPI></tt> is the EAPI of the ebuild.</p>
<p>The EAPI used by the ebuild is the EAPI included in the filename if it is set.
@@ -281,9 +288,9 @@
with EAPI Y.</p>
</div>
<div class="section" id="summary-of-ideas">
-<h1><a class="toc-backref" href="#id13">Summary of ideas</a></h1>
+<h1><a class="toc-backref" href="#id14">Summary of ideas</a></h1>
<div class="section" id="eapi-suffixed-ebuilds-proposed-solution">
-<h2><a class="toc-backref" href="#id14">EAPI-suffixed ebuilds (proposed solution)</a></h2>
+<h2><a class="toc-backref" href="#id15">EAPI-suffixed ebuilds (proposed solution)</a></h2>
<dl class="docutils">
<dt>Properties:</dt>
<dd><ul class="first last simple">
@@ -295,7 +302,7 @@
<p>Some say it is clear and simple, others that it is ugly and unintuitive.</p>
</div>
<div class="section" id="eapi-in-the-filename-with-one-time-extension-change">
-<h2><a class="toc-backref" href="#id15">EAPI in the filename with one-time extension change</a></h2>
+<h2><a class="toc-backref" href="#id16">EAPI in the filename with one-time extension change</a></h2>
<p>One of the proposed filename formats:
<tt class="docutils literal"><span class="pre"><PKG>-<VER>.eapi-<EAPI>.eb</span></tt></p>
<dl class="docutils">
@@ -310,7 +317,7 @@
<p>Some say it is better because the extension is static.</p>
</div>
<div class="section" id="easily-fetchable-eapi-inside-the-ebuild">
-<h2><a class="toc-backref" href="#id16">Easily fetchable EAPI inside the ebuild</a></h2>
+<h2><a class="toc-backref" href="#id17">Easily fetchable EAPI inside the ebuild</a></h2>
<dl class="docutils">
<dt>Properties:</dt>
<dd><ul class="first last simple">
@@ -364,7 +371,7 @@
(when only the lowest version is visible) is uncommon.</p>
</div>
<div class="section" id="easily-fetchable-eapi-inside-the-ebuild-and-one-time-extension-change">
-<h2><a class="toc-backref" href="#id17">Easily fetchable EAPI inside the ebuild and one-time extension change</a></h2>
+<h2><a class="toc-backref" href="#id18">Easily fetchable EAPI inside the ebuild and one-time extension change</a></h2>
<dl class="docutils">
<dt>Properties:</dt>
<dd><ul class="first last simple">
@@ -378,7 +385,7 @@
because of the arbitrary format restrictions in what is a bash script otherwise.</p>
</div>
<div class="section" id="use-different-subdirectories-for-different-eapis-i-e-cat-pkg-eapix">
-<h2><a class="toc-backref" href="#id18">Use different subdirectories for different EAPIs, i.e. cat/pkg/eapiX/</a></h2>
+<h2><a class="toc-backref" href="#id19">Use different subdirectories for different EAPIs, i.e. cat/pkg/eapiX/</a></h2>
<dl class="docutils">
<dt>Properties:</dt>
<dd><ul class="first last simple">
@@ -393,7 +400,7 @@
</div>
</div>
<div class="section" id="references">
-<h1><a class="toc-backref" href="#id19">References</a></h1>
+<h1><a class="toc-backref" href="#id20">References</a></h1>
<table class="docutils footnote" frame="void" id="glep54" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
@@ -410,7 +417,7 @@
</table>
</div>
<div class="section" id="copyright">
-<h1><a class="toc-backref" href="#id20">Copyright</a></h1>
+<h1><a class="toc-backref" href="#id21">Copyright</a></h1>
<p>This document has been placed in the public domain.</p>
<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
</div>
@@ -419,7 +426,7 @@
<div class="footer">
<hr class="footer" />
<a class="reference external" href="glep-0055.txt">View document source</a>.
-Generated on: 2010-04-07 22:12 UTC.
+Generated on: 2012-05-09 07:02 UTC.
Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
</div>
1.6 xml/htdocs/proj/en/glep/glep-0055.txt
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0055.txt?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0055.txt?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0055.txt?r1=1.5&r2=1.6
Index: glep-0055.txt
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0055.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- glep-0055.txt 17 May 2009 20:56:53 -0000 1.5
+++ glep-0055.txt 9 May 2012 19:37:01 -0000 1.6
@@ -1,9 +1,9 @@
GLEP: 55
Title: Use EAPI-suffixed ebuilds (.ebuild-EAPI)
-Version: $Revision: 1.5 $
-Last-Modified: $Date: 2009/05/17 20:56:53 $
+Version: $Revision: 1.6 $
+Last-Modified: $Date: 2012/05/09 19:37:01 $
Author: Piotr Jaroszyński <peper@gentoo.org>
-Status: Draft
+Status: Rejected
Type: Standards Track
Content-Type: text/x-rst
Created: 17-Dec-2007
@@ -15,6 +15,13 @@
-- Alexander Pope, An Essay on Criticism
+Status
+======
+
+This GLEP was voted down by the Council in its meeting on 2010-08-23.
+The Council rejected it again in its meeting on 2012-05-08, in favour
+of parsing the EAPI from the bash assignment statement in ebuilds.
+
Abstract
========
1.24 xml/htdocs/proj/en/glep/gleps.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/gleps.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/gleps.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/gleps.xml?r1=1.23&r2=1.24
Index: gleps.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/gleps.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- gleps.xml 10 Aug 2010 00:50:03 -0000 1.23
+++ gleps.xml 9 May 2012 19:37:01 -0000 1.24
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/gleps.xml,v 1.23 2010/08/10 00:50:03 robbat2 Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/gleps.xml,v 1.24 2012/05/09 19:37:01 ulm Exp $ -->
<!DOCTYPE gleps SYSTEM "/dtd/gleps.dtd">
<gleps>
@@ -166,7 +166,7 @@
<glep file="glep-0054.html" id="54" type="S" status="D">
scm package version suffix
</glep>
-<glep file="glep-0055.html" id="55" type="S" status="D">
+<glep file="glep-0055.html" id="55" type="S" status="R">
Use EAPI-suffixed ebuilds (.ebuild-EAPI)
</glep>
<glep file="glep-0056.html" id="56" type="S" status="F">
reply other threads:[~2012-05-09 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120509193701.B3C7C2004B@flycatcher.gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.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