From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: Re: [RFC] What features should be included in EAPI 2?
Date: Mon, 01 Sep 2008 18:31:25 +0400 [thread overview]
Message-ID: <1220279485.6005.22.camel@localhost> (raw)
In-Reply-To: <b41005390808211926i6dff4557q93d32a06f1e7146d@mail.gmail.com>
В Чтв, 21/08/2008 в 19:26 -0700, Alec Warner пишет:
> src_prepare is a logically distinct action (maybe if we called it
> src_patch it would be clearer?)
We are not only patching sources there but modify them by other means
too (like sed or find .. rm \{\};). So src_prepare is the name which
better reflects intention.
В Втр, 19/08/2008 в 12:12 +0100, Steve Long пишет:
> Besides saving one line of typing, what is the benefit of adding this
> new phase?
Although this disagreement is already closed I'd like to point that
sometimes it's more than one line:
http://overlays.gentoo.org/dev/pva/browser/x11-apps/gxneur/gxneur-0.9.0_p106.ebuild
Also... well Ryan already made the point I was going to write. :)
--
Peter.
next prev parent reply other threads:[~2008-09-01 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 8:18 [gentoo-dev] [RFC] What features should be included in EAPI 2? Zac Medico
2008-08-13 12:03 ` Ciaran McCreesh
2008-08-13 21:02 ` Zac Medico
2008-08-19 11:12 ` [gentoo-dev] " Steve Long
2008-08-19 12:45 ` Ciaran McCreesh
2008-08-19 18:01 ` Arun Raghavan
2008-08-19 18:18 ` Ciaran McCreesh
2008-08-19 20:27 ` [gentoo-dev] " Steve Long
2008-08-19 20:43 ` Ciaran McCreesh
2008-08-21 15:35 ` [gentoo-dev] " Steve Long
2008-08-21 15:58 ` Ciaran McCreesh
2008-08-22 2:26 ` Alec Warner
2008-08-23 14:15 ` [gentoo-dev] " Steve Long
2008-09-01 14:31 ` Peter Volkov [this message]
2008-08-27 3:15 ` [gentoo-dev] " Ryan Hill
2008-08-21 17:37 ` Thomas Anderson
2008-08-13 20:28 ` [gentoo-dev] " Petteri Räty
2008-08-13 21:07 ` Zac Medico
2008-08-13 22:55 ` Petteri Räty
2008-08-25 20:03 ` Jorge Manuel B. S. Vicetto
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=1220279485.6005.22.camel@localhost \
--to=pva@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