From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New eclass proposal: auto-export
Date: Thu, 23 Apr 2009 01:24:50 -0700 [thread overview]
Message-ID: <20090423082450.GF7821@hrair> (raw)
In-Reply-To: <49EF1D29.2010601@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Wed, Apr 22, 2009 at 04:35:37PM +0300, Petteri R??ty wrote:
> Here's an eclass proposal to wrap EXPORT_FUNCTIONS with auto detection
> of functions. This way all eclasses don't have to duplicate the EAPI
> detection code. If people find this useful, I will document it properly
> with eclass-manpages etc.
Mind you I follow the "Keep It Simple Stupid", but is this really
needed? In other words, how often do people really hit this?
If it's useful, whatever, but I can see the inverse of the problem
you're trying to solve occuring- folks being told to use autoexport,
then wondering how to block something from being exported...
Neutral towards it, just seems a bit much imo.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-04-23 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 13:35 [gentoo-dev] New eclass proposal: auto-export Petteri Räty
2009-04-22 13:48 ` Petteri Räty
2009-04-22 16:30 ` Arun Raghavan
2009-04-22 17:30 ` Petteri Räty
2009-04-23 8:24 ` Brian Harring [this message]
2009-04-23 11:20 ` Petteri Räty
2009-06-03 16:24 ` Maciej Mrozowski
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=20090423082450.GF7821@hrair \
--to=ferringb@gmail.com \
--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