From: "René Neumann" <lists@necoro.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Add HEXCHAT_PLUGINS to USE_EXPAND
Date: Wed, 27 Mar 2013 14:35:52 +0100 [thread overview]
Message-ID: <5152F5B8.7060907@necoro.eu> (raw)
In-Reply-To: <514B06A2.8000803@politeia.in>
Am 21.03.2013 14:09, schrieb Denis M.:
> Hello, I'd want to ask if it's possible and a good idea to add
> HEXCHAT_PLUGINS to the global USE_EXPAND var.
I personally don't think this is a good idea. Imho USE_EXPAND should be
used for flags that will be used by multiple (>5?) packages -- for the
simple reason, that USE_EXPAND somewhat hints for using /etc/make.conf
for configuration (yes, you can still use package.use, but this feature
is probably not so well known). Also the bug gives no reasoning, why
having USE_EXPAND is a good thing here.
- René
next prev parent reply other threads:[~2013-03-27 13:35 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 ` René Neumann [this message]
2013-03-28 10:09 ` [gentoo-dev] " Gilles Dartiguelongue
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=5152F5B8.7060907@necoro.eu \
--to=lists@necoro.eu \
--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