public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: NP-Hardass <NP-Hardass@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation
Date: Fri, 27 May 2016 17:08:56 -0400	[thread overview]
Message-ID: <5748B768.1090105@gentoo.org> (raw)
In-Reply-To: <1464358866.13834.59.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1898 bytes --]

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 dubious political or aesthetical reasons.
> 
> For the latter cases, despite GNOME teams policy and strong preference
> on not providing a choice and just choosing gtk2 or gtk3 (gtk3 if it's
> working as good as gtk2), some cases exist where the maintainers want
> to provide such choice. In some cases it is understandable for a short
> while during transition, e.g firefox. In other cases, it is purely for
> the sake of providing the choice of working with a deprecated toolkit,
> apparently.
> 
> My highly biased essay aside, we need to finally globally agree on what
> we do in this situation. If we allow this choice at all, only for
> special cases, or widespread. And if this choice is provided, how do we
> name the USE flag.
> 
I don't see the benefit of forcing people off of gtk2 to gtk3 when gtk2
is working just fine.  gtk2 is entrenched, and will take a while to
migrate apps from.  A parallel, why don't we just drop python2.7?  It's
old, superseded, and plenty of things support python3.x.  I disagree
with this logic.  In my opinion, we should remove support for them when
it seems that it has been dropped by a majority of packages or unfixed
security issues make it not worth keeping around.  I don't think we are
anywhere near that point.

[...]

> Thoughts? Agreements? Suggestions?
> I'm particularly interested in QA opinion here. I believe WilliamH
> wanted to spearhead this from their side.
> 
> 
> Regards,
> Mart Raudsepp
> Gentoo developer, GNOME team
> 

Flag specific comments to follow in WilliamH's reply.

-- 
NP-Hardass


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-05-27 21:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 14:21 [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation Mart Raudsepp
2016-05-27 15:02 ` Brian Dolbec
2016-05-27 16:35   ` Canek Peláez Valdés
2016-05-27 17:17     ` Brian Dolbec
2016-05-27 15:34 ` Ian Stakenvicius
2016-05-27 15:40 ` William Hubbs
2016-05-27 17:28   ` rindeal
2016-05-27 18:23   ` M. J. Everitt
2016-05-27 21:22   ` NP-Hardass
2016-05-27 15:56 ` Patrick Lauer
2016-05-27 16:15 ` Austin English
2016-05-27 16:54 ` landis blackwell
2016-05-27 16:59   ` rindeal
2016-05-27 17:14     ` Anthony G. Basile
2016-05-27 17:44       ` William Hubbs
2016-05-27 17:55         ` Anthony G. Basile
2016-05-27 21:09           ` William Hubbs
2016-05-27 18:23       ` Mart Raudsepp
2016-05-27 18:28         ` Ian Stakenvicius
2016-05-27 19:06       ` Daniel Campbell
2016-05-30 15:17       ` Mart Raudsepp
2016-05-27 18:10 ` waltdnes
2016-05-27 18:26   ` Mart Raudsepp
2016-05-27 18:44     ` rindeal
2016-05-27 18:51       ` [gentoo-dev] [RFC] improper use of X Ian Stakenvicius
2016-05-27 18:57 ` [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation Daniel Campbell
2016-05-27 21:45   ` NP-Hardass
2016-05-27 22:05     ` Daniel Campbell
2016-05-27 22:21       ` NP-Hardass
2016-05-30 20:46         ` Joakim Tjernlund
2016-06-06 15:37           ` NP-Hardass
2016-05-27 21:08 ` NP-Hardass [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5748B768.1090105@gentoo.org \
    --to=np-hardass@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox