From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE=gui?
Date: Mon, 16 Apr 2012 11:22:22 +0300 [thread overview]
Message-ID: <4F8BD6BE.9030002@gentoo.org> (raw)
In-Reply-To: <20120416101102.6de21e5c@pomiocik.lan>
On 04/16/2012 11:11 AM, Michał Górny wrote:
> On Tue, 10 Apr 2012 09:12:16 +0200
> ""Paweł Hajdan, Jr.""<phajdan.jr@gentoo.org> wrote:
>
>> On 4/10/12 8:58 AM, Pacho Ramos wrote:
>>> Other option would be to enable "wxwidgets" by default for that
>>> profiles.
>>
>> I prefer this. Changing USE flag meaning in a counter-intuitive way
>> (to let "gtk" mean "wxwidgets") would seem frustrating to me.
>>
>> With "wxwidgets" enabled by default people will get the most likely
>> desired result (i.e. GUI) "out of the box", and setting
>> USE="-wxwidgets" will have desired effect.
>>
>> Note that with USE="gtk" really meaning USE="wxwidgets", -wxwidgets
>> would have no effect on such a package, which is the potentially
>> surprising behavior I mentioned earlier.
>
> On the other hand, we should ask ourselves whether the USE flags are
> very intuitive right now.
>
> Say, we have USE=ssl which enables SSL support. We already agreed
> that's the correct meaning of it, and USE=gnutls,openssl,nss are just
> to be used when there's more than one implementation to choose from.
USE=ssl is also meaning OpenSSL and there should be no USE=openssl
>
> Shouldn't we have USE=gui in a similar fashion? Most of the devs
> probably prefer the way 'I want GUI only if it's using my favorite
> toolkit'. But users OTOH may prefer saying 'I want GUI in this app, no
> matter what it uses'.
>
> This would probably handle the wxwidgets case most correct, having it
> under USE=gui or similar.
>
-1, this would only add inconsistency / complexity to tree with packages
having multiple graphical toolkits to pick from
should be kept the way it is
- Samuli
next prev parent reply other threads:[~2012-04-16 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 6:58 [gentoo-dev] About how to handle wxGTK based packages with gnome profiles Pacho Ramos
2012-04-10 7:12 ` "Paweł Hajdan, Jr."
2012-04-10 20:21 ` Pacho Ramos
2012-04-11 6:12 ` [gentoo-dev] " Ryan Hill
2012-04-11 10:02 ` Samuli Suominen
2012-04-15 16:59 ` Pacho Ramos
2012-04-16 5:58 ` Ryan Hill
2012-04-16 8:38 ` Pacho Ramos
2012-04-16 8:11 ` [gentoo-dev] USE=gui? (was: About how to handle wxGTK based packages with gnome profiles) Michał Górny
2012-04-16 8:22 ` Samuli Suominen [this message]
2012-04-16 14:49 ` [gentoo-dev] USE=gui? Alexis Ballier
2012-04-16 17:12 ` Michał Górny
-- strict thread matches above, loose matches on Subject: below --
2015-09-09 7:20 [gentoo-dev] www-client/chromium gtk3 support Paweł Hajdan, Jr.
2015-09-09 7:24 ` Daniel Campbell
2015-09-09 10:37 ` hasufell
2015-09-10 6:21 ` Daniel Campbell
2015-09-10 8:47 ` hasufell
2015-09-10 18:15 ` Daniel Campbell
2015-09-10 18:21 ` hasufell
2015-09-10 18:26 ` Rich Freeman
2015-09-11 9:03 ` Daniel Campbell
2015-09-11 12:13 ` Rich Freeman
2015-09-11 17:11 ` [gentoo-dev] " Duncan
2015-09-11 17:41 ` Rich Freeman
2015-09-11 18:03 ` [gentoo-dev] USE="gui" Ian Stakenvicius
2015-09-11 18:16 ` Rich Freeman
2015-09-11 20:34 ` hasufell
2015-09-11 23:52 ` Daniel Campbell
2015-09-12 11:47 ` hasufell
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=4F8BD6BE.9030002@gentoo.org \
--to=ssuominen@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