public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Add HEXCHAT_PLUGINS to USE_EXPAND
Date: Thu, 28 Mar 2013 11:09:12 +0100	[thread overview]
Message-ID: <1364465352.29015.2.camel@gilles.gandi.net> (raw)
In-Reply-To: <5152F5B8.7060907@necoro.eu>

Le mercredi 27 mars 2013 à 14:35 +0100, René Neumann a écrit :
> Also the bug gives no reasoning, why
> having USE_EXPAND is a good thing here.
> 

Maybe IUSE_EXPAND is seen by most as namespaced USE flags ?
For example libgphoto2 has used this feature for as long as I can
remember it being around, and no package using it rely on them.

-- 
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo



      reply	other threads:[~2013-03-28 10:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 13:09 [gentoo-dev] Add HEXCHAT_PLUGINS to USE_EXPAND Denis M.
2013-03-26 21:28 ` [gentoo-dev] " Denis M.
2013-03-27 12:52   ` Gilles Dartiguelongue
2013-03-27 13:16     ` Markos Chandras
2013-03-28 13:56     ` Zac Medico
2013-03-28 22:49       ` Denis M.
2013-03-27 13:35 ` [gentoo-dev] " René Neumann
2013-03-28 10:09   ` Gilles Dartiguelongue [this message]

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=1364465352.29015.2.camel@gilles.gandi.net \
    --to=eva@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