From: "Rémi Cardona" <remi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Calling unknown commands in an ebuild
Date: Mon, 08 Feb 2010 08:48:24 +0100 [thread overview]
Message-ID: <4B6FC1C8.70502@gentoo.org> (raw)
In-Reply-To: <201002072124.49047.vapier@gentoo.org>
Le 08/02/2010 03:24, Mike Frysinger a écrit :
> if we wanted to specifically target semi-common errors (and i think 'epatch'
> w/out eutils.eclass falls into this category), then a repoman check would be
> good.
>
> it might also be useful to add a default epatch() to the initial env that
> would be clobbered when the inherit occurred.
> epatch() { die "you need to inherit eutils.eclass to use epatch" ; }
+1, that's a very good idea! I've stopped counting how many times that's
happened to me.
I'm sure there are other common mistakes we all do, but this particular
one is a low-hanging fruit.
Cheers,
Rémi
next prev parent reply other threads:[~2010-02-08 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 21:10 [gentoo-dev] Calling unknown commands in an ebuild Stelian Ionescu
2010-02-07 22:19 ` Zac Medico
2010-02-08 0:56 ` Stelian Ionescu
2010-02-08 1:45 ` Tomas Touceda
2010-02-08 2:24 ` Mike Frysinger
2010-02-08 7:48 ` Rémi Cardona [this message]
2010-02-08 10:18 ` Peter Volkov
2010-02-08 2:22 ` 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=4B6FC1C8.70502@gentoo.org \
--to=remi@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