From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] autotools.eclass eautomake update
Date: Tue, 25 May 2010 00:53:45 +0300 [thread overview]
Message-ID: <4BFAF569.8050009@gentoo.org> (raw)
In-Reply-To: <AANLkTik6CHMPxY-Nxi-lrZ4negdf0dUViIkpowUG1Fub@mail.gmail.com>
On 24.5.2010 23.51, Mike Frysinger wrote:
> On Mon, May 24, 2010 at 4:44 AM, Petteri Räty wrote:
>> On 24.5.2010 1.54, Mike Frysinger wrote:
>>> ive updated eautomake to run automake in a few more edge cases. hopefully
>>> this doesnt break anything else (seems to not on my system), but who knows.
>>>
>>> if you see random eautoreconf/eautomake failure, try backing out the
>>> autotools.eclass change first.
>>
>> I think any autotools.eclass behavior changes would benefit from being
>> sent to gentoo-dev for review first.
>
> if i felt most people had an understanding of how autotools worked let
> alone how autotools.eclass, then perhaps i would
> -mike
>
And what do you loose by sending them here? The devmanual text strictly
doesn't enforce it but strongly encourages: "Before updating eutils or a
similar widely used eclass, it is best to email the gentoo-dev list."
http://devmanual.gentoo.org/eclass-writing/index.html
Regards,
Petteri
next prev parent reply other threads:[~2010-05-24 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 22:54 [gentoo-dev] autotools.eclass eautomake update Mike Frysinger
2010-05-24 8:44 ` Petteri Räty
2010-05-24 20:51 ` Mike Frysinger
2010-05-24 21:53 ` Petteri Räty [this message]
2010-05-24 22:17 ` Mike Frysinger
2010-05-25 6:54 ` Rémi Cardona
2010-05-25 7:23 ` Mike Frysinger
2010-05-25 19:22 ` Rémi Cardona
2010-05-25 19:37 ` Mike Frysinger
2010-05-25 7:46 ` Peter Volkov
2010-05-25 12:12 ` [gentoo-dev] " Duncan
2010-05-25 12:45 ` Peter Volkov
2010-05-25 12:59 ` Pacho Ramos
2010-05-25 20:02 ` [gentoo-dev] " Petteri Räty
2010-05-25 20:12 ` Mike Frysinger
2010-05-25 20:38 ` Petteri Räty
2010-05-25 21:00 ` Mike Frysinger
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=4BFAF569.8050009@gentoo.org \
--to=betelgeuse@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