Ühel kenal päeval, L, 21.05.2016 kell 11:19, kirjutas
waltd...@waltdnes.org:
> On Sat, May 21, 2016 at 09:41:28AM +0200, Micha?? Górny wrote
> > 3. We remove LINGUAS from USE_EXPAND and stop using it. If ebuilds
> > have
> > a good reason to use flags for localization, we introduce a new,
> > non-c
On Fri, 27 May 2016 00:28:35 +0200
rindeal wrote:
> 1) what are they?
A horrible QA violation.
> 2) why are they used?
Because some people like to feel special...
--
Ciaran McCreesh
Hello,
Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
upstream, many applications still support only gtk2, have subtle issues
with their gtk3 port, or support both, with some of our userbase
clinging to gtk2 for dubious political or aesthetical reasons.
For the latter cases
On Fri, May 27, 2016 at 9:28 AM, Kent Fredric wrote:
> That said, its a very confusing system to get your head around,
> because its *basically* yet another "mixin" system like "inherit", but
> done in bash, which itself is a rather strange language to be doing
> something as complicated as mixins
On Fri, 27 May 2016 17:21:06 +0300
Mart Raudsepp wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle
> issues with their gtk3 port, or support both, with some of our
> userbase clinging to gt
On 27/05/16 10:21 AM, Mart Raudsepp wrote:
> [ Snip! ]
Agree on all other portions above; its the Applications part below
that is most contentious though and is also what I care most about:
> * Applications may only use a gtk2 based stack or gtk3 based stack in a
> given version/revision. gtk3
On Fri, May 27, 2016 at 05:21:06PM +0300, Mart Raudsepp wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle issues
> with their gtk3 port, or support both, with some of our userbase
> clinging
On 05/27/2016 04:21 PM, Mart Raudsepp wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle issues
> with their gtk3 port, or support both, with some of our userbase
> clinging to gtk2 for dubious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/27/2016 09:21 AM, Mart Raudsepp wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle issues
> with their gtk3 port, or support both, with s
On Fri, May 27, 2016 at 10:02 AM, Brian Dolbec wrote:
[snip]
> I'll be really sad when gtk2 is totally abolished in Gentoo. :(
> I suppose I'll have to break down and switch to KDE maybe.
>
> In my opinion the upstream gtk developers have gone somewhat bonkers
> with their cartoonish changes to th
I stopped reading after you reminded me it was 2016
On May 27, 2016 9:21 AM, "Mart Raudsepp" wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle issues
> with their gtk3 port, or support both,
On 27 May 2016 at 18:54, landis blackwell wrote:
> I stopped reading after you reminded me it was 2016
Good to know, thanks for stopping by.
On 5/27/16 12:59 PM, rindeal wrote:
> On 27 May 2016 at 18:54, landis blackwell wrote:
>> I stopped reading after you reminded me it was 2016
>
> Good to know, thanks for stopping by.
>
Yeah the "its year" meme has been making its rounds of the
internet.
anyhow, my 2017 question is about avah
On Fri, 27 May 2016 11:35:01 -0500
Canek Peláez Valdés wrote:
> On Fri, May 27, 2016 at 10:02 AM, Brian Dolbec
> wrote: [snip]
> > I'll be really sad when gtk2 is totally abolished in Gentoo. :(
> > I suppose I'll have to break down and switch to KDE maybe.
> >
> > In my opinion the upstream gtk
> (qa hat in place)
>
> There is a qa policy about this. All packages in the tree should
> move away from the non-versioned gtk use flag to versioned use flags,
> like the ones the qt team uses [1] [2].
>
> This seems to be the best compromise. It allows the maintainers of the
> packages to decide
I've found some more info on this topic from the internet archive.
- "[gentoo-dev] RFC: eblits.eclass"
http://news.gmane.org/find-root.php?message_id=4BC0F659.7000506%40gentoo.org
- https://github.com/transtone/zm-overlay/blob/master/eclass/eblits.eclass
- https://wiki.gentoo.org/wiki/GLEP:33
- "R
On Fri, May 27, 2016 at 01:14:17PM -0400, Anthony G. Basile wrote:
> On 5/27/16 12:59 PM, rindeal wrote:
> > On 27 May 2016 at 18:54, landis blackwell wrote:
> >> I stopped reading after you reminded me it was 2016
> >
> > Good to know, thanks for stopping by.
> >
>
> Yeah the "its year" meme
On 5/27/16 1:44 PM, William Hubbs wrote:
> On Fri, May 27, 2016 at 01:14:17PM -0400, Anthony G. Basile wrote:
>> On 5/27/16 12:59 PM, rindeal wrote:
>>> On 27 May 2016 at 18:54, landis blackwell wrote:
I stopped reading after you reminded me it was 2016
>>>
>>> Good to know, thanks for stoppi
On Fri, May 27, 2016 at 05:21:06PM +0300, Mart Raudsepp wrote
> This would ideally not be needed, as the package would instead be
> slotted and parallel installable for gtk2 and gtk3, which should be
> theoretically possible in all cases, because gtk2 and gtk3 may not live
> in the same process, s
On 27/05/16 16:40, William Hubbs wrote:
> On Fri, May 27, 2016 at 05:21:06PM +0300, Mart Raudsepp wrote:
>> Hello,
>>
>> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
>> upstream, many applications still support only gtk2, have subtle issues
>> with their gtk3 port, or suppo
Ühel kenal päeval, R, 27.05.2016 kell 13:14, kirjutas Anthony G.
Basile:
> On 5/27/16 12:59 PM, rindeal wrote:
> > On 27 May 2016 at 18:54, landis blackwell > m> wrote:
> > > I stopped reading after you reminded me it was 2016
> >
> > Good to know, thanks for stopping by.
> >
>
> Yeah the "its
Ühel kenal päeval, R, 27.05.2016 kell 14:10, kirjutas
waltd...@waltdnes.org:
> While we're at it, why are there 23 occurences of the "X" useflag
> in
> /usr/portage/profiles/use.local.desc when it exists in
> /usr/portage/profiles/use.desc ??? I'm talking about stuff like...
>
> app-misc/vifm:X
On 27/05/16 02:23 PM, Mart Raudsepp wrote:
> If gtk2 support is removed though, then per gnome policy gtk3 component
> should come with USE=gtk and per QA policy USE=gtk3.
>
> The QA policy is not finalized and completely contradicts our side of
> things, hence discussions are needed, but did not
On 27 May 2016 at 20:26, Mart Raudsepp wrote:
> Ühel kenal päeval, R, 27.05.2016 kell 14:10, kirjutas
> waltd...@waltdnes.org:
>> While we're at it, why are there 23 occurences of the "X" useflag
>> in
>> /usr/portage/profiles/use.local.desc when it exists in
>> /usr/portage/profiles/use.desc ??
On 27/05/16 02:44 PM, rindeal wrote:
>
> It also clearly shows how is this flag misused:
>
> dev-python/PyQt4:X - Build bindings for the QtGui module
> dev-python/pyside:X - Build QtGui and QtTest modules
> media-gfx/fbida:X - Install the Motif based image viewer "ida"
> media-video/aravis:X - Bu
On 05/27/2016 07:21 AM, Mart Raudsepp wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle issues
> with their gtk3 port, or support both, with some of our userbase
> clinging to gtk2 for dubiou
On 05/27/2016 10:14 AM, Anthony G. Basile wrote:
> On 5/27/16 12:59 PM, rindeal wrote:
>> On 27 May 2016 at 18:54, landis blackwell wrote:
>>> I stopped reading after you reminded me it was 2016
>>
>> Good to know, thanks for stopping by.
>>
>
> Yeah the "its year" meme has been making its round
On 05/23/2016 12:54 PM, Michał Górny wrote:
> ---
> eclass/git-r3.eclass | 53
> +++-
> 1 file changed, 52 insertions(+), 1 deletion(-)
>
> diff --git a/eclass/git-r3.eclass b/eclass/git-r3.eclass
> index 957ff08..61218a8 100644
> --- a/eclass/git-
On Fri, May 27, 2016 at 01:55:41PM -0400, Anthony G. Basile wrote:
> On 5/27/16 1:44 PM, William Hubbs wrote:
> > On Fri, May 27, 2016 at 01:14:17PM -0400, Anthony G. Basile wrote:
> >> On 5/27/16 12:59 PM, rindeal wrote:
> >>> On 27 May 2016 at 18:54, landis blackwell
> >>> wrote:
> I stopp
On 05/27/2016 10:21 AM, Mart Raudsepp wrote:
> Hello,
>
> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
> upstream, many applications still support only gtk2, have subtle issues
> with their gtk3 port, or support both, with some of our userbase
> clinging to gtk2 for dubiou
On 05/27/2016 11:40 AM, William Hubbs wrote:
> On Fri, May 27, 2016 at 05:21:06PM +0300, Mart Raudsepp wrote:
>> Hello,
>>
>> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
>> upstream, many applications still support only gtk2, have subtle issues
>> with their gtk3 port, or
On 05/27/2016 02:57 PM, Daniel Campbell wrote:
> As far as I'm concerned, if any package I maintain offers both gtk2 and
> gtk3 support, it would be irresponsible for me to *not* offer that
> choice. Gentoo is about flexibility and giving power to the user. Choice
> is a central part of that, and b
On 05/27/2016 02:45 PM, NP-Hardass wrote:
> On 05/27/2016 02:57 PM, Daniel Campbell wrote:
>> As far as I'm concerned, if any package I maintain offers both gtk2 and
>> gtk3 support, it would be irresponsible for me to *not* offer that
>> choice. Gentoo is about flexibility and giving power to the
On 05/27/2016 06:05 PM, Daniel Campbell wrote:
> On 05/27/2016 02:45 PM, NP-Hardass wrote:
>> Not on hand, but as the MATE maintainer, I can tell you that starting
>> with MATE-1.14, two packages are gtk3 only, and starting with 1.16, four
>> more are.
>>
>
> Aha, thanks for offering that info. W
On 28 May 2016 at 05:35, rindeal wrote:
> This whole concept, however, raises the question (as suggested by
> Ciaran McCreesh and Duncan) if it's allowed to split ebuilds to
> several bash scripts and what have QA and dev-manual got to say in
> this regard?
Personally I'd say the biggest risk fr
35 matches
Mail list logo
