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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
Summary of Gentoo council meeting 11 March 2014
Agenda
======
1. Roll call
2. Open issues - vote on GLEP 63
3. Ban on EAPI 1 and 2 should extend to updating EAPI in existing ebuilds
4. Make all cosmetic repoman warnings fatal
5. Adherence to FHS standards in Gentoo: putting config files int /etc
6. Bugs assigned to Council
7. Open floor
1. Roll call
============
Present: blueness dberkholz dilfridge rich0 ulm williamh
Absent: scarabeus
2. Open issues - vote on GLEP 63
================================
Previous council action approved in principle the policies outlined in
"GLEP 63: Gentoo GPG key policies" [1], but delayed the vote for approval
until the final language was put in place. dilfridge presented a shorter
version of the GLEP which removed the "howto" language and reduced it to
just policy [2]. Discussion progressed to a consensus that we should have
only policy in the GLEP and a practical guide should be a separate document
which can be changed without council vote.
We tabled the vote until either an email vote (initiated by dilfridge) or
the next meeting.
Ref:
[1] https://wiki.gentoo.org/wiki/GLEP:63
[2] https://wiki.gentoo.org/wiki/User:Dilfridge/GLEP:1001a
3. Ban on EAPI 1 and 2 should extend to updating EAPI in existing ebuilds
=========================================================================
The council considered the question of whether the ban on EAPIs 1 and 2 should
extended to updating EAPIs in *existing* ebuilds, and not just new ebuilds added
to the tree [3]. mgorny noted that we need bumps from EAPI 0 to 1 because we need
an easy way to introduce slotting without the major rewriting of ebuild phases
than an EAPI 0 to 3 bump would require. After discussion, the council voted on
the following motion:
"EAPI 1 and 2 are now banned. This ban should not only be limited to new ebuilds,
but should be extended to include updating EAPIs in *existing* ebuilds. In case
of non-maintainer commits to fix dependencies, EAPI=0 ebuilds may be updated to
EAPI=1 to keep the changes at a non-intrusive level, as a temporary workaround."
The motion carried with 4 yes, 1 no and 1 abstention.
Ref:
[3] http://permalink.gmane.org/gmane.linux.gentoo.project/3382
4. Make all cosmetic repoman warnings fatal
===========================================
The council considered the question of whether all repoman warnings should be
made fatal [4]. Consensus was reached that this would lead to too many false
positives.
The motion failed with 4 no and 1 abstention.
Ref:
[4] http://permalink.gmane.org/gmane.linux.gentoo.project/3358
5. Adherence to FHS standards in Gentoo: putting config files int /etc
======================================================================
The question of where config files should go was raised by patrick [5,6,7]. The
council discussed whether it should be policy to put all config files in /etc.
However, what defines a config file is unclear because some packages, like udev or
eudev, put their *default* config files in /lib/udev/rules.d which are overridden
by the files in /etc/udev/rules.d. The former are not meant to be user-edited while
the later are. The council is okay with static config files living outside of /etc
while user-editable config files should be in /etc.
rich0 introduced the following motion:
"Council does not feel additional policy required regarding config files in /etc.
In particular packages that place config templates in /usr or /lib* and allow overriding
in /etc are fine. Specific issues not already discussed can be raised in future meetings."
The motion passed with 4 yes and 1 abstention.
Ref:
[5] http://permalink.gmane.org/gmane.linux.gentoo.project/3357
[6] http://permalink.gmane.org/gmane.linux.gentoo.project/3367
[7] http://devmanual.gentoo.org/general-concepts/filesystem/index.html
6. Bugs assigned to Council
===========================
The council looked at two open bugs:
a) Bug #503382 - Missing summaries for 20131210, 20140114, and 20140225 council meetings
dberkholz said he would upload those summaries soon.
b) Bug #477030 - Missing summary for 20130611 council meeting
There has been no progress. scarabeus was to nudge betelgeuse for that summary.
7. Open floor
=============
No issues were brought forward.
Summary submitted by Anthony G. Basile <blueness@gentoo.org>
|
GitWeb