
\summary{2008}{9}{25}


\agendaitem{EAPI 2}
\index{EAPI!2}\index{EAPI!2!approval}

Goal: Vote on approval

Requirements: 
\begin{itemize}
 \item
 Put a generated copy (preferably HTML) in the PMS project webspace. 
    People who want to refer to an EAPI=2 reference don't necessarily 
    want to install all the dependencies to build it.
 \item
 Let's tag the git repository something like 
    eapi-\$EAPI-approved-\$DATE.
\end{itemize}

Result: EAPI=2 is approved.


\agendaitem{PROPERTIES in cache}
\index{PROPERTIES}\index{metadata cache}

Goal: Vote: Does council need to approve cache changes?

Goal: Vote on approval

Result: Since it's related to the EAPI, this should be another issue 
that package-manager developers resolve amongst themselves and only 
present to council if they can't agree.

They agree on adding it to the cache as a value that package managers 
can ignore, so it is.


\agendaitem{PROPERTIES=interactive in ebuilds}

Goal: Vote: Does council need to approve global-variable changes in 
      ebuilds?

Result: This is a retroactive, backwards-compatible EAPI change and thus 
is handled the same as any other EAPI change -- it requires council 
approval.

Goal: Vote on approval

Result: PROPERTIES=interactive is approved.
