Label profiles with EAPI for compatibility checks
-------------------------------------------------

An EAPI=0 profile always needs to exist so that users with old portage 
can upgrade. Otherwise they will sync and have no valid profile 
available so cannot emerge a new version of portage.

Decision: Approved. Existing stable profiles must use EAPI=0. New or dev 
profiles can use higher EAPIs.

Ref: http://archives.gentoo.org/gentoo-dev/msg_930f58fcebcbbcbe523c001f2c825179.xml


EAPI change: Call ebuild functions from trusted working directory
-----------------------------------------------------------------

dberkholz didn't think it needed council approval to add something to 
EAPI=0 that exists in all the PMs.

Decision: Approved

Ref: http://archives.gentoo.org/gentoo-dev/msg_5ba467bbd5a0820e040210683702a67f.xml


DEFINED_PHASES magic metadata variable
--------------------------------------

There are no uses of USE-conditional functions in the main tree.

Decision: Approved. Let's get portage support, then have infra 
regenerate the whole cache with this.

Ref: http://archives.gentoo.org/gentoo-dev/msg_8c34d8efbc0d31ab28c517403dc83f62.xml