From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Place of EAPI variable in ebuild
Date: Fri, 9 Nov 2007 22:04:23 +0000 [thread overview]
Message-ID: <20071109220423.6db37ff4@blueyonder.co.uk> (raw)
In-Reply-To: <4734D767.1080900@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Fri, 09 Nov 2007 23:55:51 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:
> Usually it's best that ebuild variables follow the order that is in
> skel.ebuild. So know we should decide where to place EAPI. I suggest
> we put it it after LICENSE as that's where the more technical stuff
> like SLOT starts. Attached a patch for skel.ebuild.
It needs to go right at the top, before 'inherit'.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-09 22:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 21:55 [gentoo-dev] RFC: Place of EAPI variable in ebuild Petteri Räty
2007-11-09 22:04 ` Ciaran McCreesh [this message]
2007-11-09 22:42 ` Petteri Räty
2007-11-09 23:00 ` [gentoo-dev] " Markus Ullmann
2007-11-10 0:10 ` Petteri Räty
2007-11-10 0:39 ` [gentoo-dev] " Carsten Lohrke
2007-11-10 0:57 ` Ciaran McCreesh
2007-11-09 22:07 ` Fabian Groffen
2007-11-11 19:01 ` Petteri Räty
2007-11-11 19:08 ` Ciaran McCreesh
2007-11-11 19:21 ` Petteri Räty
2007-11-11 19:27 ` Ciaran McCreesh
2007-11-11 20:50 ` Fabian Groffen
2007-11-11 21:04 ` Ciaran McCreesh
2007-11-11 23:27 ` Carsten Lohrke
2007-11-13 20:22 ` Chris Gianelloni
2007-11-13 20:31 ` Ciaran McCreesh
2007-11-14 0:17 ` Chris Gianelloni
2007-11-14 0:39 ` Ciaran McCreesh
2007-11-14 0:46 ` Ciaran McCreesh
2007-11-14 1:25 ` Chris Gianelloni
2007-11-14 1:34 ` Ciaran McCreesh
2007-11-14 1:39 ` Josh Saddler
2007-11-14 0:58 ` Petteri Räty
2007-11-12 23:11 ` Petteri Räty
2007-11-12 23:13 ` Petteri Räty
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=20071109220423.6db37ff4@blueyonder.co.uk \
--to=ciaran.mccreesh@blueyonder.co.uk \
--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