public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds
Date: Fri, 13 Nov 2009 12:43:25 +0100	[thread overview]
Message-ID: <19197.18013.751396.332003@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: 20091019194459.GY464@gentoo.org

In its November meeting [1], the council has unanimously expressed
support for this proposal [2].

However, there is need for additional discussion. From the council
meeting log I could extract the following open questions:

  1. What are the implications for non-prefix devs and users? 

  2. Should the Prefix team be allowed to do the necessary changes to
     ebuilds themselves, or should it be done by the respective
     maintainers?

  3. Are there any backwards compatibility or upgrade path issues for
     eclasses that must still accept EAPI 0 (where the new ED, EROOT,
     and EPREFIX variables are not defined)?

  4. EAPI numbering: Would this simply be added as an additional
     feature to EAPI 3? Or should we have an intermediate EAPI slot,
     e.g. 2.1 or 3 (and current EAPI 3 renamed to 4 in the latter
     case)?

  5. Who is going to write the exact specification (PMS patch) for
     this EAPI feature?

  6. (Any question that I've missed?)

Let's start the discussion now, in order to work out these details
before the next council meeting (December 7th).

Ulrich

[1] <http://www.gentoo.org/proj/en/council/meeting-logs/20091109.txt>
    (topic was discussed from 21:32 to 22:11 in the log's timezone)
[2] <http://archives.gentoo.org/gentoo-dev/msg_2a62689c71f95e4de5699a330b8b5524.xml>



  parent reply	other threads:[~2009-11-13 11:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  9:11 [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds Fabian Groffen
2009-10-18 11:57 ` Tomáš Chvátal
2009-10-18 12:31   ` Fabian Groffen
2009-10-19 19:44     ` Fabian Groffen
2009-10-24 19:37       ` Petteri Räty
2009-10-24 20:00         ` Fabian Groffen
2009-11-13 11:43       ` Ulrich Mueller [this message]
2009-11-20  8:45         ` Fabian Groffen
2009-11-20  0:26 ` Denis Dupeyron
2009-11-20  1:42   ` Jeremy Olexa
2009-11-20  9:03     ` Fabian Groffen
2009-11-25 23:43       ` Denis Dupeyron
2009-11-26  8:53         ` Fabian Groffen
2009-11-26 10:01           ` [gentoo-dev] " Duncan
2009-11-26 10:10             ` Fabian Groffen
2009-11-26 10:37               ` Duncan
2009-11-26 10:51                 ` Fabian Groffen
2009-11-26 12:36                   ` Duncan
2009-11-26 15:26                     ` Fabian Groffen
2009-11-26 13:43         ` [gentoo-dev] " Fabian Groffen
2009-11-26  0:01   ` Denis Dupeyron
2009-11-26  9:02     ` Fabian Groffen

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=19197.18013.751396.332003@a1i15.kph.uni-mainz.de \
    --to=ulm@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