\summary{2008}{12}{11}

Agenda call: \agoref{gentoo-dev}{0e772bcdd84f62690f331f84ccc7c12d}

Agenda announcement: \agoref{gentoo-dev}{30b46e4fd22d14a02d469ebcf63f4c8c}


\agendaitem{Label profiles with EAPI for compatibility checks}
\index{EAPIs!in profiles}

Reference: \agoref{gentoo-dev}{930f58fcebcbbcbe523c001f2c825179}

Should there be labels in the profiles telling package managers what EAPI the 
profile uses. This proposal raised some concerns that developers would modify 
current profiles and bump the EAPI which would harm users' systems.

Conclusion: Profile EAPI files are approved for use in gentoo-x86 profiles. The 
file for use in profiles is 'eapi'. All current profiles are EAPI="0" and only 
new profiles can be marked with the profile EAPI markers. Any developer 
profiles can be marked with a new EAPI.

            
\agendaitem{Retroactive EAPI change: Call ebuild functions from trusted working
      directory}
\index{EAPI!0}\index{EAPI!1}\index{EAPI!2}\index{package!sys-apps/portage}
\index{package!sys-apps/paludis}

Reference: \agoref{gentoo-dev}{5ba467bbd5a0820e040210683702a67f}

As detailed in the e-mail, the following sentence shall be added to PMS section 
10.1:
\begin{quote}
The ebuild can rely that the chosen initial working direcotry is a trusted 
location that is not world-writable and owned by a privileged user and group.
\end{quote}
This is related to fixing \bug{239560}, and implemented in Portage since 
versions 2.1.4.5 and 2.2_rc12, Paludis since version 0.30.2.

Conclusion: Unanimously approved. This change applies to all current EAPIs 
(0,1,2).


\agendaitem{Metadata variable for DEFINED_PHASES}
\index{metadata cache}\index{DEFINED_PHASES}

Reference: \agoref{gentoo-dev}{8c34d8efbc0d31ab28c517403dc83f62}

Should a metadata variable be added containing the list of all phases defined 
in the ebuild or eclasses?

Conclusion: Approved. Infra will do a full regeneration of the metadata cache 
once portage has support for the extra field.