1 |
Apologies for sending the summary this late. |
2 |
|
3 |
|
4 |
Summary of Gentoo council meeting 14th August 2012 |
5 |
|
6 |
Roll call |
7 |
========= |
8 |
betelgeuse |
9 |
chainsaw |
10 |
grobian |
11 |
scarabeus |
12 |
ulm |
13 |
williamh |
14 |
|
15 |
absent |
16 |
------ |
17 |
dberkholz (receives slacker mark) |
18 |
|
19 |
|
20 |
EAPI5 features |
21 |
============== |
22 |
Due to holidays, the list of features for EAPI5 was announced only 2 |
23 |
days in advance of the meeting. This gave little time for Council |
24 |
members to prepare for votes. |
25 |
Therefore a vote was conducted if voting on EAPI5 features in this |
26 |
meeting was deemed suitable. |
27 |
|
28 |
The Council voted unanimously to postpone voting on EAPI5 features. |
29 |
|
30 |
The list of features for EAPI5 were outlined by ulm in |
31 |
http://thread.gmane.org/gmane.linux.gentoo.project/2101/focus=2115 |
32 |
Since many of these features appear not to be implemented in Portage, a |
33 |
discussion on their implementation is called for by the Council. The |
34 |
Council stressed that it prefers to vote on EAPI5 features that can and |
35 |
will be implemented within a short timeframe, say 1 month. |
36 |
|
37 |
|
38 |
Open bugs with Council involvement |
39 |
================================== |
40 |
There are currently no open bugs. |
41 |
|
42 |
|
43 |
Open floor |
44 |
========== |
45 |
scarabeus suggested the change "dev should use latest eapi when bumping" |
46 |
to "dev must use latest eapi when bumping if not forbidden by eclasses". |
47 |
He was asked to bring it up on the mailing lists, to get a better |
48 |
definition of when what EAPI should be used. |
49 |
|
50 |
ulm raised deprecation of EAPI 1 on request of patrick. Arfrever argued |
51 |
that backwards compatability is not an issue here, and that it can |
52 |
greatly reduce code size/maintenance of eclasses when EAPI0 and EAPI1 |
53 |
are removed. It was questioned whether removal of an EAPI really brings |
54 |
that much benefits. It seems eclasses can drop support for EAPIs, if |
55 |
all consumers don't use them, which does not require complete removal of |
56 |
the EAPI. It appears some packages use build-systems that require |
57 |
EAPI1. |
58 |
|
59 |
|
60 |
Next meeting date |
61 |
================= |
62 |
11 September 2012, 19:00 UTC |
63 |
|
64 |
|
65 |
-- |
66 |
Fabian Groffen |
67 |
Gentoo on a different level |