From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-71910-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 1FAED138453
for <garchives@archives.gentoo.org>; Wed, 9 Sep 2015 15:00:41 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 6B55521C01D;
Wed, 9 Sep 2015 15:00:31 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 862F821C011
for <gentoo-dev@lists.gentoo.org>; Wed, 9 Sep 2015 15:00:30 +0000 (UTC)
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
(Authenticated sender: floppym)
by smtp.gentoo.org (Postfix) with ESMTPSA id DD5DA34089F
for <gentoo-dev@lists.gentoo.org>; Wed, 9 Sep 2015 15:00:28 +0000 (UTC)
Received: by igcrk20 with SMTP id rk20so102177406igc.1
for <gentoo-dev@lists.gentoo.org>; Wed, 09 Sep 2015 08:00:26 -0700 (PDT)
X-Received: by 10.50.70.34 with SMTP id j2mr54821108igu.54.1441810826568; Wed,
09 Sep 2015 08:00:26 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.107.20.85 with HTTP; Wed, 9 Sep 2015 08:00:07 -0700 (PDT)
In-Reply-To: <55EFDDAD.9030502@gentoo.org>
References: <55EFDDAD.9030502@gentoo.org>
From: Mike Gilbert <floppym@gentoo.org>
Date: Wed, 9 Sep 2015 11:00:07 -0400
Message-ID: <CAJ0EP43ugNTptHmaJZaBkCLU57ro1Jk+fbBirjd1dAJHCVAr7Q@mail.gmail.com>
Subject: Re: [gentoo-dev] www-client/chromium gtk3 support
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 83ba237f-6fbb-4f9c-81f1-615e977dbdee
X-Archives-Hash: 552878cec6fe5d8104ce7fec5ae4e651
On Wed, Sep 9, 2015 at 3:20 AM, Pawe=C5=82 Hajdan, Jr. <phajdan.jr@gentoo.o=
rg> wrote:
> A user asked for optional gtk3 support in www-client/chromium:
> <https://bugs.gentoo.org/show_bug.cgi?id=3D559378>
>
> However, reading e.g.
> <https://wiki.gentoo.org/wiki/Project:GNOME/Gnome_Team_Ebuild_Policies#gt=
k3>
> says this:
>
>> having USE=3Dgtk3 to enable gtk+-3 instead of gtk+-2 support is
>> forbidden
>
>> package is an application with support for multiple gtk+, maintainer
>> is free to select whatever slot he desires to support. It is strongly
>> advised to use gtk+-3 if functionality is equivalent. This is to
>> reduce workload of bugs being triggered with one slot but not the
>> other.
>
> What are your recommendations for the best course of action?
>
> For stability and maintainability, I'd prefer www-client/chromium to use
> the upstream defaults (gtk+-2 AFAIK) since it's most common, tested, and
> supported configuration. If/when upstream moves to gtk+-3, we'd just foll=
ow.
>
> I also understand we have users who are eager to run various
> configurations, and expect Gentoo to be flexible and allow that. Would
> masking a gtk3 USE flag for www-client/chromium be acceptable? Are there
> any other solutions that might work?
I would really like a way to toggle gtk3 for testing. If you don't
want to expose it as a 'supported' option for users, then masking it
sounds fine to me.