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{2010}{11}{30}
Agenda call: \agoref{gentoo-project}{02f133c3f1ef09e5ec04f055b5cf5ba7}
Agenda announcement: \agoref{gentoo-project}{d5f9f86f7f8051379cc164207bf1f222}
\agendaitem{Future meetings}
\index{council!meeting!schedule}
The council members have discussed internally alternating between Tuesdays and
Saturdays, because \dev{halcy0n} can't do weekdays and \dev{chainsaw} can't do
weekends. During the meeting it turned out that \dev{chainsaw} can attend on
Saturdays, although the timing is then really hard for \dev{ferringb}.
The council decided to have the next meeting on Saturday the 18th of December,
at 1500 UTC. \dev{jmbsvicetto} will chair. We'll keep switching between Tuesdays
and Saturdays for the time being to try and accomodate all members.
\agendaitem{EAPI 4}
\index{EAPI!4}\index{MERGING_FROM}\index{PMS}
\index{REPLACED_VERSIONS}\index{REPLACED_BY_VERSION}
\index{pkg_pretend}\index{EAPI!usage in ebulds}\index{EAPI!deprecation}
The council agreed that the current EAPI-4_pre1 implementation is pretty good.
Some clarifications concerning REPLACED_VERSIONS and REPLACED_BY_VERSION and the
impact of the new pkg_pretend phase were discussed.
\dev{ulm} will work on a PMS patch for EAPI-4. He will create a final tag, that
will also include one extra feature, a variable called MERGING_FROM, available
in pkg_* phases, with the following possible values: ["source","binary"].
The tag will then be approved by the council, either by email or in a meeting,
whatever is faster. Our goal is to have EAPI-4 before 2010 ends.
On a related note, a discussion about deprecating EAPIs and the QA
recommendation on which EAPI to use for new ebuilds was started.
\agendaitem{Libtool archive (.la) files removal status/progress}
\index{.la files}\index{package!sys-devel/libtool}
Nothing has happened since the last meeting. \dev{jmbsvicett} did start some
mailing list threads, but there was no interest in the subject.
The following needs to be done:
\begin{enumerate}
\item write documentation (with \dev{flameeyes}'s blog as source),
\item publish a news item,
\item get portage 2.1.9 stable, and
\item let developers remove .la files.
\end{enumerate}
Since no-one volunteered to do step 1, the topic was pushed to the mailing
lists.
|
GitWeb
