public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: AllenJB <gentoo-lists@allenjb.me.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: "X" vs "gtk" USE flags
Date: Mon, 08 Feb 2010 15:22:00 +0000	[thread overview]
Message-ID: <4B702C18.40709@allenjb.me.uk> (raw)
In-Reply-To: <hkp5he$37f$1@ger.gmane.org>

On 08/02/10 14:02, Nikos Chantziaras wrote:
> On 02/08/2010 03:41 PM, AllenJB wrote:
>> On 08/02/10 12:32, Nikos Chantziaras wrote:
>>> On 02/08/2010 01:39 PM, Samuli Suominen wrote:
>>>> IMHO. USE="X" is for controlling X.org dependencies, not for avoiding
>>>> everything that deps on them, so I disagree.
>>>
>>> I was under the impression that USE flags are for enabling/disabling
>>> features, not for controlling deps.  DEPEND and RDEPEND is, AFAIK, the
>>> way to control deps.
>>>
>>>
>> Features influence dependencies. If you enable kde features the package
>> will require kde dependencies. So use flags and dependencies are
>> irrevocably linked.
>>
>> What Samuli is saying is that the X flag should be specifically for X
>> (and not X-related, such as graphical libraries) features, while the kde
>> and gtk use flags should remain in use as they are. This way when you
>> see "X" as a use flag, you know it means "enable X features" and isn't
>> likely to pull in anything but X libraries, if you see "kde" you know it
>> means "enable kde features" and isn't likely to pull in anything but kde
>> libraries, and so on.
> 
> So I guess what I was really proposing then was a "gui" USE flag :P
> Sorry about that, I didn't fully understand the meaning of the X flag.
> 
> 
And what purpose would this flag server that's not already covered by
using USE="X fltk qt gtk kde gnome" (and possibly a couple of others
I've forgotten about) - which are all already in the desktop profile,
which the vast majority of people who don't care what toolkit they get
will already be using anyway?

The current system caters perfectly for both people who want to avoid
specific toolkits and those who don't care what toolkits they use.

AllenJB



  reply	other threads:[~2010-02-08 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 11:15 [gentoo-dev] "X" vs "gtk" USE flags Nikos Chantziaras
2010-02-08 11:30 ` Tomáš Chvátal
2010-02-08 11:39   ` Samuli Suominen
2010-02-08 12:32     ` [gentoo-dev] " Nikos Chantziaras
2010-02-08 13:41       ` AllenJB
2010-02-08 14:02         ` Nikos Chantziaras
2010-02-08 15:22           ` AllenJB [this message]
2010-02-08 18:26             ` Ben de Groot
2010-02-08 18:28             ` Ben de Groot
2010-02-08 19:21             ` Nikos Chantziaras
2010-02-08 11:36 ` [gentoo-dev] " AllenJB
2010-02-08 12:12   ` [gentoo-dev] " Nikos Chantziaras
2010-02-08 12:16     ` Samuli Suominen
2010-02-08 12:38       ` Nikos Chantziaras
2010-02-08 12:10 ` [gentoo-dev] " Mike Frysinger
2010-02-08 12:11 ` [gentoo-dev] " Christian Faulhammer
2010-02-08 12:34   ` Nikos Chantziaras
2010-02-08 15:40     ` William Hubbs
2010-02-08 21:39   ` Jeroen Roovers

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=4B702C18.40709@allenjb.me.uk \
    --to=gentoo-lists@allenjb.me.uk \
    --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