blob: f1d49db263dcf4b337ef1e420e47ec3c70bdfeaa (
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
81
|
\summary{2011}{1}{11}
Agenda call: \agoref{gentoo-project}{1f0e1006dff86ed5466838093acb1bea}
Agenda announcement: \agoref{gentoo-project}{046560a972cd72dc5b4911f07007e973}
\agendaitem{New council member}
\dev{halcy0n} stepped down from the council a few days before this meeting.
The council unanimously accepted \dev{patrick}, the next in line, to fill
the empty seat, with this being his first meeting.
\agendaitem{-{}-disable-dependency-tracking}
\index{EAPI!5}\index{EAPI!4}\index{disable-dependency-tracking}\index{econf}
\index{--disable-dependency-tracking}
Reference: \bug{211529}
Since EAPI 4, econf automatically appends ``--disable-dependency-tracking'' to
the configure call. Unfortunately only automake-based build systems support the
option, leading to warnings. As summarized in \bug{211529} by \dev{ulm}, the
possible options are:
\begin{enumerate}
\item
to only filter the warning for now, and reiterate for EAPI 5, as suggested
by \dev{betelgeuse} in comment \#12.
\item
to change the specification as in the attached patch
\item
to call {\tt ./configure --help | grep disable-dependency-tracking} to
determine if the option is available (another idea from \dev{flameeyes}).
\item
to remove --disable-dependency-tracking from EAPI 4 entirely.
\end{enumerate}
\dev{betelgeuse} expressed some concern about option 3 as it would mean
changing an approved EAPI version. \dev{ferringb} and \dev{jmbvicetto}
expressed the view
that the council can just issue a new tag and that EAPI 4 has not been
approved for use yet. No council member supported option 4. \dev{feringb} and
\dev{blueness} noted that option 2 only partially addresses the issue.
The vote turned out 6 votes for option 3 and 1 vote for option 1.
\agendaitem{use_with 3-argument specification}
\index{use_with}\index{EAPI!0}\index{EAPI!1}\index{EAPI!2}\index{EAPI!3}
\index{EAPI!4}
Reference: \bug{322049}
\dev{jmbvicetto} asked for a clarification about the proposal to address this
bug. \dev{ferringb} explained that the purpose is to change EAPI 0 to 3
definition to state that {\tt use_with arg1 arg2 ''} can't be relied upon.
For EAPI 4 it can be relied on. So in EAPI 0-3, use_with arg1 arg2 ''
is treated as if there were two args, whilst in EAPI 4 it is treated as
if there were 3 arguments.
All council members approved the proposal.
\agendaitem{EAPI 4 tree usage approval}
\index{EAPI!4!approval}
The council members decided to wait for a new portage release that
will include the above modifications before approving EAPI-4 for tree
use. Some members expressed the desire to hold the aprroval until said
portage release is marked stable, but no decision was made. The issue
will be resolved and approval will be granted via email or at the next
meeting.
\agendaitem{Slacking arches}
\index{arches!slacking}
There was some discussion about this issue, but the council members
decided that this needs to be discussed on the -dev mailing list before the
council can decide anything about this topic.
|
GitWeb