summaryrefslogtreecommitdiff
blob: 96cd0f7ec66a839256af2ae08d9eaeecd7ae6119 (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
82
83
84
85
86
87
\summary{2015}{10}{11}

\agendaitem{EAPI 4 deprecation}
\index{EAPI!4!deprecation}\index{EAPI!4}

Reference: \agoref{gentoo-project}{b5b7aa83ddd64fdfa84284c1ceddcec6}

By unanimous agreement EAPI 4 is declared deprecated.


\agendaitem{Behaviour of asterisk with = dependency operator}
\index{= dependencies}\index{PMS}

References: 
\begin{itemize}
 \item 
 \agoref{gentoo-project}{65abf95ef1ea05a1aa3bc716be386a64}
 \item
 \bug{560466}
 \item 
\url{
https://gitweb.gentoo.org/proj/portage.git/commit/?id=d4966a381ee4577818bd972946
647338046715b1}
\end{itemize}

By unanimous vote, the proposed PMS modification is introduced 
retroactively for all EAPIs.

By the current description of the * operator in PMS, a dependency 
cat/foo-1.2* matches cat/foo-1.2, cat/foo-1.2.1, etc. but it also 
matches cat/foo-1.20. The definition in PMS is updated such that 
version components cannot be split when matching (i.e. 1.2* would not 
match 1.20).


\agendaitem{Runtime dependencies and dynamic dependency deprecation}
\index{dynamic dependencies}\index{dependencies!dynamic}

References: 
\begin{itemize}
 \item 
 \agoref{gentoo-project}{a8b5b499b9dbfdaea57a8f2a158c1fe7}
 \item
 http://article.gmane.org/gmane.linux.gentoo.devel/97742 (dead link)
 \item
 http://thread.gmane.org/gmane.linux.gentoo.devel/97428/focus=97742 (dead link)
\end{itemize}

\vote{Maintainers must not assume that dynamic dependencies will be applied 
by the package manager. When changing runtime dependencies the 
maintainer should revision the ebuild if the changes are likely to 
cause problems for end users.}{Accepted unanimous.}

The details, in particular the explicit rules proposed by rich0 on the
gentoo-devel mailing list, were referred back to the list for further
discussion and should eventually become recommendations. Further
decisions on policies may also be up to the QA team.


\agendaitem{Games policies}
\index{games!policies}\index{games!group}\index{games!install paths}

Reference: \agoref{gentoo-project}{16fc54d2bced9ff51b71d387eb0fb36b}

After some discussion on the details of FHS, the merit of separate
users and directories for games and our Gentoo directory structure, 
the following votes as proposed by rich0 were taken:

\vote{Decide that games should not be owned by a games group, and that
in the default configuration users should not have to be in the games
group to run games.}{
Motion accepted with 6 yes and 1 abstention}

\vote{Games should be installed in /usr and not /usr/games as with most
applications}{
Motion not passed, 2 yes, 2 no and 3 abstentions}


\agendaitem{Games bugzilla component}
\index{bugzilla}\index{games!bugzilla component}

Reference: \agoref{gentoo-project}{2175a9dde8a1fb614ccb75c60c43c8c8}

By unanimous vote the 'Games" component of bugzilla will be assigned
by default to bug wranglers instead of the games team.