Gentoo Archives: gentoo-project

From: Samuli Suominen <ssuominen@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Agenda for Gentoo Council meeting on 2014-02-25
Date: Tue, 25 Feb 2014 16:18:45
Message-Id: 530CC1C8.6030702@gentoo.org
In Reply to: Re: [gentoo-project] Re: [gentoo-dev-announce] Agenda for Gentoo Council meeting on 2014-02-25 by Rich Freeman
1 On 25/02/14 18:12, Rich Freeman wrote:
2 > On Tue, Feb 25, 2014 at 10:27 AM, Mart Raudsepp <leio@g.o> wrote:
3 >> We acknowledge that our policy may not have been perfect but we need
4 >> time to analyze claims brought up by/to the QA team to construct a
5 >> proper proposal for a better policy that would satisfy everyone;
6 >> hopefully in co-operation with a QA team.
7 > Is there any reason to think that this analysis will come to a
8 > different conclusion?
9 >
10 > I don't see any concerns on the list that weren't addressed already.
11 > USE=gtk2 means build gtk2 support
12 > USE=gtk3 means build gtk3 support
13 > USE="gtk2 gtk3" means build support for whichever version the
14 > maintainer thinks is better (which is what USE=gtk meant a week ago)
15
16 And how does one select 'the best supported GTK+ for this application,
17 selected by the package's maintainer.' ?
18 I want latest best supported GTK+ enabled for all of my packages. I
19 can't figure out the USE combination from
20 those. You can't surely assume every user to review every single package
21 and decide for himself after reading
22 hours, days, weeks, if not even months various package ChangeLogs, NEWS
23 files, and other possible ways
24 upstreams are communicating with? And how does user know of all the mail
25 that goes between upstream
26 and package maintainers about what to choose for distribution?
27
28 >
29 > If there is something that has been missed I'm happy to hear it, but
30 > it has been a week and I haven't seen anything beyond the "why can't
31 > maintainers choose?" theme which was responded to a week ago. If
32 > there are other objections we should consider, then please state them
33 > before the meeting. I'm sure somebody might think of something new,
34 > but it has been a week and somebody could think of something new 9
35 > months from now.
36 >
37 >
38
39 It doesn't cover the case of 'functionality', only 'baseless want of an
40 clueless user for restoration of old theme look'

Replies