Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] mercurial-native: add recipe
Date: Tue, 07 Sep 2010 07:29:36 +0100	[thread overview]
Message-ID: <4C85DBD0.9050708@xora.org.uk> (raw)
In-Reply-To: <AANLkTi=LswfyrP_t-5G2iipd6umjkAmdwFiECLmZXMXW@mail.gmail.com>

 On 07/09/10 07:27, Frans Meulenbroeks wrote:
> 2010/9/6 Eric Bénard <eric@eukrea.com>:
>> * mercurial is a distributed SCM
>> * having the native recipe inside OpenEmbedded gives the
>> possibility to fetch code from mercurial's repositories
>> without the need to have mercurial installed on the host
>>
>> Signed-off-by: Eric Bénard <eric@eukrea.com>
>> ---
>>  recipes/mercurial/mercurial-native_1.6.3.bb |   23 +++++++++++++++++++++++
>>  1 files changed, 23 insertions(+), 0 deletions(-)
>>  create mode 100644 recipes/mercurial/mercurial-native_1.6.3.bb
>>
>> diff --git a/recipes/mercurial/mercurial-native_1.6.3.bb b/recipes/mercurial/mercurial-native_1.6.3.bb
>> new file mode 100644
>> index 0000000..58fcaf1
>> --- /dev/null
>> +++ b/recipes/mercurial/mercurial-native_1.6.3.bb
>> @@ -0,0 +1,23 @@
>> +DESCRIPTION = "The Mercurial distributed SCM"
>> +SECTION = "console/utils"
>> +LICENSE = "GPLv2"
>> +
>> +SRC_URI = "http://mercurial.selenic.com/release/mercurial-${PV}.tar.gz;name=src"
>> +
>> +DEPENDS = "python-native"
>> +PR = "r0"
>> +
>> +S = "${WORKDIR}/mercurial-${PV}"
>> +EXTRA_OEMAKE = "STAGING_LIBDIR=${STAGING_LIBDIR} STAGING_INCDIR=${STAGING_INCDIR} \
>> +       BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} PREFIX=${STAGING_DIR_NATIVE}/usr"
>> +
>> +do_install () {
>> +        install -d ${STAGING_DIR_NATIVE}/usr
> I'm a little bit surprised that you need this. I had expected install
> to take care of that.
> Otherwise, the recipe looks fine to me (but haven't test-build it yet)
>
Missed the original mail, but the install -d line should be in
do_install_prepend()

This makes it clearer that its a hack. You then also wont need to
specify the oe_runmake install bit.

Graeme




  reply	other threads:[~2010-09-07  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 21:41 [PATCH 1/2] mercurial-native: add recipe Eric Bénard
2010-09-06 21:41 ` [PATCH 2/2] base.bbclass: depend on mercurial-native if SRC_URI contains hg:// Eric Bénard
2010-09-07  6:27 ` [PATCH 1/2] mercurial-native: add recipe Frans Meulenbroeks
2010-09-07  6:29   ` Graeme Gregory [this message]
2010-09-07  8:07   ` Eric Bénard
2010-09-07  9:32   ` [PATCH v2] " Eric Bénard

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=4C85DBD0.9050708@xora.org.uk \
    --to=dp@xora.org.uk \
    --cc=openembedded-devel@lists.openembedded.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