blob: 1cdee86ebdced08453444d04bd2dfd2a269311dc (
plain)
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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
\summary{2009}{5}{28}
Agenda call and announcement:
\agoref{gentoo-dev}{9543319301d55b1e3f362d72ef1b92c1}
\agendaitem{Filling the empty council seat}
\index{council!members}
\dev{dberkholz} resigned from the council so there is an empty spot that needs
to be filled. \dev{ssuominen} and \dev{ulm} were tied for the next spot, but
\dev{ssuominen} relinquished his seat to \dev{ulm}. To fill the spot, \dev{ulm}
needed to be unanimusly voted in by the current members.
Conclusion: Unanimously voted to fill the seat. \dev{ulm} will fill
\dev{dberkholz}'s seat for the rest of the current term.
\agendaitem{EAPI 3 status report from Zac Medico}
\index{EAPI!3}
No progress yet. \dev{zmedico} said he'd have a recent recruit of his work with
him on it.
Conclusion: Zac will work on EAPI 3 features with the help of his recruit. He
will also blog about what features need to be done so the general community can
pitch in.
\agendaitem{Removal of Old Eclasses}
\index{eclasses!removal}
\dev{jmbsvicetto} requested that the council discuss removing eclasses from the
tree that are no longer needed. The problem with this is that old ($<2.1.4$)
portage versions used the eclasses from the tree to run uninstall phases. Thus,
the removal of eclasses would break users who have a portage older than
2.1.4.\footnote{Portage 2.1.4 was stabilized in March 2008, see \bug{210031}.}
Conclusion: The council voted that to remove eclasses devs should take the
following steps:
\begin{enumerate}
\item
Deprecate eclasses.
\item
Removal of all functionality relating to installing.
\item
After two years the eclass may be removed.
\end{enumerate}
\dev{tanderson} will write up patches for the devmanual so that this policy is
documented.
\agendaitem{Handling EAPI Versioning in a forwards-compatible way}
Various developers have raised concerns that \glep{55} only describes a solution
and doesn't clearly show the problems being solved (if any). \dev{lu_zero}
mentioned a few things in the "Problem" section that he thought could be
clarified, listed below:
\begin{enumerate}
\item
For "Change the behaviour of inherit in any way", it would be useful to
include references to bugs where requested inherit changes would require
\glep{55}.
\item
For "Add new global scope functions in any way", defining 'Sane'.
\item
For "Extend versioning rules in an EAPI", removal of all mentions of \glep{54}
would remove circularity. In addition, mentioning other version format changes
would be useful.
\item
For "Use newer bash features", listing useful (including in-tree) bash
features not available in the bash version mandated by PMS would be
useful.\index{bash!features in ebuilds}
\end{enumerate}
Conclusion: The council voted on whether they recognized the problem that
\glep{55} is attempting to solve is real. The vote was affirmative in
recognition of the problem with two abstentions. \dev{cardoe} was no longer at
the meeting for this vote and will post his vote on-list.
|
GitWeb