From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-71965-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 EC28F138454
for <garchives@archives.gentoo.org>; Fri, 11 Sep 2015 12:13:56 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 7C93321C015;
Fri, 11 Sep 2015 12:13:50 +0000 (UTC)
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com [209.85.223.175])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 82276E0869
for <gentoo-dev@lists.gentoo.org>; Fri, 11 Sep 2015 12:13:49 +0000 (UTC)
Received: by iofh134 with SMTP id h134so95487158iof.0
for <gentoo-dev@lists.gentoo.org>; Fri, 11 Sep 2015 05:13:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:content-type;
bh=KDLsdEPZq8MQGzK81b4LxJ5JY0IyF90vzLvBsYXwuGM=;
b=aiSDg9s0YBrJg+ofHvqFMIj3ftPjHAm/nIeg+ORR7PT9rfX5Ty50RNiBLl7cKGiIbx
kFebDlpncf/2YZPiSTalJdxdUSMmxQdCUJt4HKEWNW34F1e48PCidyoTg1YRew3entJH
G7VgfwqhzL/pVZtBgFhxqSYFD8sq3kQ+5GAxKgvaaDP+1wa5yy/vFuJUEkbu4A2IHB3K
n0A3oXeBI/znmbZEiHP9lB6v7XkBMb91wM1kUVzbvbpfOLDUbKwvWtqkKBjZV9ZNyIE5
C0oQKD8fgiMZ41Sab9WIm1UDCnVCbi1BhnZUqJqjR5qjjHkRAi/b5zraoZBssAZZ7z9I
J0zA==
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
X-Received: by 10.107.46.101 with SMTP id i98mr3186625ioo.17.1441973628805;
Fri, 11 Sep 2015 05:13:48 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.79.103.70 with HTTP; Fri, 11 Sep 2015 05:13:48 -0700 (PDT)
In-Reply-To: <55F298D0.7020702@gentoo.org>
References: <55EFDDAD.9030502@gentoo.org>
<55EFDEC7.1070403@gentoo.org>
<55F00BFD.7050804@gentoo.org>
<55F12159.3020506@gentoo.org>
<55F1439E.1070002@gentoo.org>
<55F1C8AB.40005@gentoo.org>
<55F1CA38.3050302@gentoo.org>
<CAGfcS_m_-gJGBC662TF0H6u23Ns+bUU4_LstLz-65ygiMDWzsw@mail.gmail.com>
<55F298D0.7020702@gentoo.org>
Date: Fri, 11 Sep 2015 08:13:48 -0400
X-Google-Sender-Auth: gu_s2xL2zlOEai7XBZYd0CR1x-I
Message-ID: <CAGfcS_khnhq1a8M6Ku+iuaD2jDgxwfkGc8QXACL2kyOg3EJVOQ@mail.gmail.com>
Subject: Re: [gentoo-dev] www-client/chromium gtk3 support
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: 3164bd31-441e-42de-81cd-2706c503fd90
X-Archives-Hash: afc2517f206eb734a1b0522c57273903
On Fri, Sep 11, 2015 at 5:03 AM, Daniel Campbell <zlg@gentoo.org> wrote:
>
> I like the general 'gtk' flag we generally use to choose *which*
> toolkit, and local USE flags for specific versions, if they are
> supported. But in that case, the general gtk flag should be
> interpreted as the latest version supported, so users don't come
> across weirdly behaving packages that default to gtk2 (unless that
> version is the most stable).
>
>...
>
> For starters, versioned USE flags more than likely don't belong in
> make.conf's USE variable and shouldn't be global.
>
That was roughly my proposal.
USE=gui or something like that if the main effect is to have a gui or
not. That is the sort of thing that SHOULD go in make.conf or in a
profile. If disabling gtk makes it a console-only application then
use the gui flag.
USE=gtk if the main effect is to select /which/ toolkit is used if
more than one is optionally supported. That /might/ go in a make.conf
or profile, but probably shouldn't in general. It is more appropriate
for something like the desktop/gnome profile than the desktop profile.
USE=gtk# if you're picking which version to use. That should /almost
never/ go in a profile (unless you're talking about a testing profile
of some kind, such as on an overlay), or in a global config unless you
REALLY know what you're getting into. Users setting this globally
should expect to run into bugs. The package should default these
flags to whatever is most appropriate for the specific package.
I'd be tempted to even say to not have gtk3 but instead call the flag
chromium-gtk3 or whatever so that it becomes very difficult to put in
the global config. However, that goes against our general principle
of letting the user break their system and keep the pieces if they
think they know what they're doing. If somebody WANTS to test out a
gtk3-only system or whatever they should have the freedom to do so,
understanding that testing sometimes uncovers problems.
Of course any change will need a transition period, news, handbook
updates, etc. For the person who wants the "just works" experience
they can pick a profile and it will do the right thing, and if they
want to tailor things a bit more the USE=(-)gui flag will do what it
would be expected to do.
--
Rich