From: Mamoru KOMACHI <usata@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Some 'proper coding' notes for ebuilds
Date: Mon, 04 Aug 2003 00:10:06 +0900 [thread overview]
Message-ID: <867k5u22wh.wl%usata@gentoo.org> (raw)
In-Reply-To: <200308022238.57835.vapier@gentoo.org>
Hi,
At Sat, 2 Aug 2003 22:38:57 -0400,
Mike Frysinger wrote:
> oooooooooh and stop trying to run the `patch` cmd yourself ...
Agreed ;-)
> no one is cooler than `epatch` (which is integrated into portage now, so dont
> 'inherit eutils'), so stop trying to think you ppl are
I'm afraid we should add 'inherit eutils' because though epatch is now
integrated into unstable version of portage, stable version of portage
(2.0.48-r5) doesn't have this functionality. I came across the
problem in http://bugs.gentoo.org/show_bug.cgi?id=23131#c11 and found
we need 'inherit eutils' for stable.
Anyhow, some of the ebuilds seem to use epatch without 'inherit
eutils' (and I guess they will fail to compile properly). I counted
that sort of ebuild using small sh script and it says 332 ebuilds use
epatch without declairing 'inherit eutlis' ;-( Well, I included both
stable and unstable ebuilds, but at least for stable we need to write
'inherit epatch' at this moment.
cf. here is the list of such ebuilds:
http://dev.gentoo.org/~usata/ebuild_wepatch_woeutils.txt
--
Mamoru KOMACHI <usata@gentoo.org>
http://dev.gentoo.org/~usata/
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-03 15:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 2:29 [gentoo-dev] Some 'proper coding' notes for ebuilds Mike Frysinger
2003-08-03 2:34 ` Mike Frysinger
2003-08-03 2:38 ` Mike Frysinger
2003-08-03 2:50 ` Kumba
2003-08-03 3:04 ` Mike Frysinger
2003-08-03 15:23 ` Martin Schlemmer
2003-08-03 18:44 ` Mike Frysinger
2003-08-03 15:10 ` Mamoru KOMACHI [this message]
2003-08-03 15:40 ` Paul de Vrieze
2003-08-03 16:23 ` Mamoru KOMACHI
2003-08-03 16:27 ` Georgi Georgiev
2003-08-03 17:04 ` Mamoru KOMACHI
2003-08-03 15:30 ` Martin Schlemmer
2003-08-11 13:45 ` Patrick Kursawe
2003-08-11 14:58 ` Mike Frysinger
2003-08-03 5:31 ` Jason A. Mobarak
2003-08-03 4:56 ` Mike Frysinger
2003-08-03 6:11 ` Luke-Jr
2003-08-03 14:55 ` Stuart Herbert
2003-08-03 15:18 ` Martin Schlemmer
2003-08-03 18:07 ` Stuart Herbert
2003-08-03 18:48 ` Mike Frysinger
2003-08-03 18:53 ` Stuart Herbert
2003-08-03 20:27 ` George Shapovalov
2003-08-03 20:34 ` Stuart Herbert
2003-08-03 22:15 ` George Shapovalov
2003-08-03 22:56 ` Don Seiler
2003-08-08 15:21 ` Anthony de Boer
2003-08-08 15:33 ` Marius Mauch
2003-08-08 18:25 ` George Shapovalov
2003-08-08 19:16 ` Douglas Russell
2003-08-08 20:12 ` George Shapovalov
2003-08-08 23:01 ` Mike Frysinger
2003-08-10 2:58 ` George Shapovalov
2003-08-03 22:19 ` Aron Griffis
[not found] ` <20030803223541.05d10e90.spider@gentoo.org>
2003-08-03 20:43 ` Stuart Herbert
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=867k5u22wh.wl%usata@gentoo.org \
--to=usata@gentoo.org \
--cc=gentoo-dev@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