From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Add HEXCHAT_PLUGINS to USE_EXPAND
Date: Thu, 28 Mar 2013 06:56:16 -0700 [thread overview]
Message-ID: <51544C00.5040505@gentoo.org> (raw)
In-Reply-To: <1364388725.24497.10.camel@gilles.gandi.net>
On 03/27/2013 05:52 AM, Gilles Dartiguelongue wrote:
> Le mardi 26 mars 2013 à 22:28 +0100, Denis M. a écrit :
>> On 03/21/2013 02:09 PM, Denis M. wrote:
>>
>>> Hello, I'd want to ask if it's possible and a good idea to add
>>> HEXCHAT_PLUGINS to the global USE_EXPAND var.
>>>
>>> HEXCHAT_PLUGINS has been created as a user (and maintainer) request
>>> in bug 461972 [1] to handle easily the net-irc/hexchat plugins that
>>> this package offers, which are: checksum, doat, fishlim and sysinfo.
>>>
>>> The purposed ebuild can be found on the bug's attached files list.
>>>
>>> Regards,
>>> Denis M. (Phr33d0m)
>>>
>>> [1] https://bugs.gentoo.org/show_bug.cgi?id=461972
>> Bump.
>>
>> Hi again, could I get a decisive answer on this please?
>
> That does not sound like a bad idea, however I wonder how this extends
> exactly if we start to do this for ebuilds which install a couple of
> plugins behind a few regular USE flags nowadays like rhythmbox, abiword,
> etc.
The only potential problem that I can think of is that it bloats the
environment with an extra variable that's exported to all ebuilds. With
older kernels, environment bloat triggered E2BIG errors, as reported in
this bug:
https://bugs.gentoo.org/show_bug.cgi?id=262647
--
Thanks,
Zac
next prev parent reply other threads:[~2013-03-28 13:56 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 [this message]
2013-03-28 22:49 ` Denis M.
2013-03-27 13:35 ` [gentoo-dev] " René Neumann
2013-03-28 10:09 ` 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=51544C00.5040505@gentoo.org \
--to=zmedico@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