Last meeting: http://www.gentoo.org/proj/en/council/meeting-logs/20090326-summary.txt


Migration of KEYWORDS out of ebuilds
------------------------------------

Ned Ludd (solar) requested at the last meeting that the council discuss 
a migration of KEYWORDS out of ebuilds to be discussed at this meeting.

Goal: Get enough detail about the idea to think about it, have some 
initial discussion.

Time allotted: 10 minutes


EAPI 3 features
---------------

Do we want to block addition of any new features to EAPI 3 and instead 
push them to EAPI 4, in the interest of getting this done now? This 
specifically applies to anything not already discussed as of last 
meeting, including the 2 below items.

Goal: Vote on this.

Time allotted: 10 minutes


EAPI 3: Inclusion of "mtime preservation"
-----------------------------------------

Ulrich Mueller wrote:

Since EAPI 3 is on the agenda already, I would ask the council to
consider inclusion of "mtime preservation" (see bug 264130, and the
thread "Preserving mtimes for EAPI3" in this ML).

As I see it, there are three options:
  A. Always preserve timestamps when merging from D to ROOT, what was my
     original suggestion. Portage and Pkgcore already comply with this.
  B. Preserve timestamps, but optionally allow the package manager to update
     "old" ones. This is the suggestion from comment #12. Again, Portage and
     Pkgcore would be compliant already (since updating mtimes would be
     optional).
  C. As B, but with mandatory updating of "old" mtimes. For this, all three
     package managers would have to be changed.


Goal: Bring up concerns. Vote on this.

Time allotted: 10 minutes


EAPI 3: Inclusion of prefix-related variables
---------------------------------------------

Fabian Groffen wrote:

I would like the council to discuss the addition of three variables to 
EAPI3.

- EPREFIX
  The offset prefix of a Gentoo Prefix installation.  When Gentoo Prefix
  is not used, ${EPREFIX} should be "".
  This variable should be available everywhere.
- EROOT
  The offset prefix appended to ${ROOT}, e.g. ${ROOT%/}${EPREFIX}/
  This variable is available where ROOT is, following PMS: pkg_*
- ED
  The offset prefix appended to ${D}, e.g. ${D%/}${EPREFIX}/
  This variable is available where D is, following PMS: src_install

While the first variable (EPREFIX) can be set using an eclass, the 
latter two need to be set by the package manager.  In particular ED, 
because the value of D might not be known.  EROOT and ED are convenience 
variables.  Making them available already now, even though initialised 
as ROOT and D respectively, allows Prefix enabled ebuilds to be shared 
between gentoo-x86 and Prefix trees without modifications.


Goal: Get opinions from council members.

Time allotted: 15 minutes


Portage changing behavior in ebuild-visible ways
------------------------------------------------

David Leverton wrote:

I would like the Council to discuss the matter of Portage repeatedly 
changing behaviour in ebuild-visible ways without an EAPI bump or even 
an announcement that anything changed.  Notable examples include .lzma 
support in unpack (bug 207193), the change in pkg_* phase ordering (bug 
222721) and the preservation of timestamps during merge (bug 264130).  
It is quite frustrating to spend considerable effort determining 
Portage's behaviour and matching it in Paludis, only to find a few 
months later that Portage changed and now users are getting broken 
packages if not broken systems because ebuilds are starting to rely on 
the new rules.

Goal: David proposes having a policy that this won't happen in the 
future or admitting that we don't really care.

Time allotted: 15 minutes


If time permits:
Update on GLEP 55
-----------------

Petteri?

Goal: Get an update on the current status of things.