[oe] [PATCH 1/2] mercurial-native: add recipe

[Frans Meulenbroeks]

2010/9/6 Eric Bénard <eric at 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 at 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)

Frans
> +        oe_runmake install
> +}
> +
> +inherit native
> +
> +SRC_URI[src.md5sum] = "fcd61edc488d1b9aa831dde6f14d9a13"
> +SRC_URI[src.sha256sum] = "57e5d26d35fbec71206378e3af111193e6eee7bb1dfb6447bbc4b9e03ce937bd"
> +
> --
> 1.6.3.3
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>