1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
\summary{2009}{10}{12}
Agenda call: \agoref{gentoo-dev}{982709dd37e8736bf639e02f033547af},
\agoref{gentoo-council}{be55f6d520fb4d0c3349f59fcc29e5e4}
Agenda announcement:
\agoref{gentoo-council}{56694fb154f6f280343dbc3c9940df8e}
\agendaitem{Why follow up for items from last meeting never happened}
\index{council!meeting!followup}
The responsibilities of volunteers, the secretary, and the meeting chair were
discussed. In the end the following motion was carried:
\vote{People volunteer to follow up but if there's none the chair takes
care of it and also reminds the volunteer}{5 yes, 1 no, 1 abstain}
\agendaitem{EAPI 3 update}
\index{EAPI!3}
\dev{zmedico} didn't attend to give any update.
\agendaitem{Preservation of file modification times}
\index{mtime preservation}
\vote{Reopening EAPI 3 for mtimes}{4 yes, 2 no, 1 abstain}
\vote{Selecting from implementation alternatives, see \bug{264130}
comment 26:
\begin{enumerate}[label=\Alph*]
\item
Always preserve timestamps when merging from D to ROOT, what was my original
suggestion. Portage and Pkgcore already comply with this.
\item
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).
\item
As B, but with mandatory updating of "old" mtimes. For this, all three package
managers would have to be changed.
\end{enumerate}
}{4 A, 1 A or B, 1 B}
\agendaitem{Open floor}
\index{multilib portage}\index{upgrade path}
Topic items:
\begin{itemize}
\item Inclusion of multilib-portage into the main portage code.
\item Upgrade paths for old systems (with respect to EAPI) --- \dev{leio} and
\dev{solar} will do follow up
\end{itemize}
|
GitWeb
