Skip to contentSkip to conversation

mercurial-native: add recipe

PATCH Superseded Eric Bénard 3 participants 6 messages Sep 6, 2010 – Sep 7, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 mercurial-native: add recipe

* 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

---
 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
recipes/mercurial/mercurial-native_1.6.3.bb new file +23 -0
new file mode 100644
index 0000000..58fcaf1
@@ -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
+        oe_runmake install
+}
+
+inherit native
+
+SRC_URI[src.md5sum] = "fcd61edc488d1b9aa831dde6f14d9a13"
+SRC_URI[src.sha256sum] = "57e5d26d35fbec71206378e3af111193e6eee7bb1dfb6447bbc4b9e03ce937bd"
+
Signature · 1 line
1.6.3.3
#1 lore raw

PATCH 2/2 base.bbclass: depend on mercurial-native if SRC_URI contains hg://

---
 classes/base.bbclass |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
classes/base.bbclass +5 -0
index 299e875..2e6fb84 100644
@@ -367,6 +367,11 @@ python () {
         depends = depends + " git-native:do_populate_sysroot"
         bb.data.setVarFlag('do_fetch', 'depends', depends, d)
 
+    if "hg://" in srcuri:
+        depends = bb.data.getVarFlag('do_fetch', 'depends', d) or ""
+        depends = depends + " mercurial-native:do_populate_sysroot"
+        bb.data.setVarFlag('do_fetch', 'depends', depends, d)
+
     # unzip-native should already be staged before unpacking ZIP recipes
     need_unzip = bb.data.getVar('NEED_UNZIP_FOR_UNPACK', d, 1)
     src_uri = bb.data.getVar('SRC_URI', d, 1)
Signature · 1 line
1.6.3.3
#2 lore raw
In reply to Eric Bénard

2010/9/6 Eric Bénard <[email protected]>:

Quoted 22 lines

* 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

---
 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

recipes/mercurial/mercurial-native_1.6.3.bb new file +5 -0
new file mode 100644
index 0000000..58fcaf1
@@ -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"

recipes/mercurial/mercurial-native_1.6.3.bb line 15

Quoted 10 lines
recipes/mercurial/mercurial-native_1.6.3.bb new file +10 -0
+
+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)

Frans

Quoted 17 lines
recipes/mercurial/mercurial-native_1.6.3.bb new file +8 -1
+        oe_runmake install
+}
+
+inherit native
+
+SRC_URI[src.md5sum] = "fcd61edc488d1b9aa831dde6f14d9a13"
+SRC_URI[src.sha256sum] = "57e5d26d35fbec71206378e3af111193e6eee7bb1dfb6447bbc4b9e03ce937bd"
+
--

1.6.3.3

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#3 lore raw
Quoted 28 lines · Frans Meulenbroeks

2010/9/6 Eric Bénard <[email protected]>:

Quoted 27 lines

* 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

---
 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
recipes/mercurial/mercurial-native_1.6.3.bb new file +10 -0
new file mode 100644
index 0000000..58fcaf1
@@ -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}"
Quoted 9 lines

recipes/mercurial/mercurial-native_1.6.3.bb line 15

Quoted 5 lines
recipes/mercurial/mercurial-native_1.6.3.bb new file +5 -0
+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

#4 lore raw
In reply to Frans Meulenbroeks

Hi Frans,

Quoted 9 lines · Frans Meulenbroeks

2010/9/6 Eric Bénard<[email protected]>:

recipes/mercurial/mercurial-native_1.6.3.bb line 15

Quoted 3 lines
recipes/mercurial/mercurial-native_1.6.3.bb new file +3 -0
+
+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)

I will remove it and retest, it may not be needed as I added that when I was trying to get the beast installed.

Eric

#5 lore raw

PATCH v2 1/1 mercurial-native: add recipe

In reply to Frans Meulenbroeks

* 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

---
v2: improve recipe + ostylize it

 recipes/mercurial/mercurial-native_1.6.3.bb |   21 +++++++++++++++++++++
 1 files changed, 21 insertions(+), 0 deletions(-)
 create mode 100644 recipes/mercurial/mercurial-native_1.6.3.bb
recipes/mercurial/mercurial-native_1.6.3.bb new file +21 -0
new file mode 100644
index 0000000..717f8f6
@@ -0,0 +1,21 @@
+DESCRIPTION = "The Mercurial distributed SCM"
+HOMEPAGE = "http://mercurial.selenic.com/"
+SECTION = "console/utils"
+LICENSE = "GPLv2"
+DEPENDS = "python-native"
+PR = "r0"
+
+SRC_URI = "http://mercurial.selenic.com/release/mercurial-${PV}.tar.gz;name=src"
+SRC_URI[src.md5sum] = "fcd61edc488d1b9aa831dde6f14d9a13"
+SRC_URI[src.sha256sum] = "57e5d26d35fbec71206378e3af111193e6eee7bb1dfb6447bbc4b9e03ce937bd"
+
+S = "${WORKDIR}/mercurial-${PV}"
+
+inherit native
+
+EXTRA_OEMAKE = "STAGING_LIBDIR=${STAGING_LIBDIR} STAGING_INCDIR=${STAGING_INCDIR} \
+        BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} PREFIX=${prefix}"
+
+do_install () {
+        oe_runmake -e install DESTDIR=${D} PREFIX=${prefix}
+}
Signature · 1 line
1.6.3.3