public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation
Date: Fri, 27 May 2016 21:26:14 +0300	[thread overview]
Message-ID: <1464373574.13834.81.camel@gentoo.org> (raw)
In-Reply-To: <20160527181048.GA4587@waltdnes.org>

Ühel kenal päeval, R, 27.05.2016 kell 14:10, kirjutas
waltdnes@waltdnes.org:
>   While we're at it, why are there 23 occurences of the "X" useflag
> in
> /usr/portage/profiles/use.local.desc when it exists in
> /usr/portage/profiles/use.desc ???  I'm talking about stuff like...
> 
> app-misc/vifm:X - Add support for X11
> dev-libs/m17n-lib:X - Builds the Graphical User Interface API and
> utilities for the package.
> dev-libs/wlc:X - Enable X11 backend and XWayland support.
> dev-python/PyQt4:X - Build bindings for the QtGui module
> dev-python/pyside:X - Build QtGui and QtTest modules

Because they specify in more details what the USE flag does
specifically, in the context of that package.
Such more exact local descriptions are something I at least personally
strongly advocate in favour of.
app-misc/vifm local desc seems redundant though, but the rest listed
here seem useful and necessary.


Mart


  reply	other threads:[~2016-05-27 18:26 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 [this message]
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

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=1464373574.13834.81.camel@gentoo.org \
    --to=leio@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