From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: multiple git repos vs. AUTOREV?
Date: Tue, 16 Jun 2015 16:40:13 +0200 [thread overview]
Message-ID: <20150616144013.GC17938@jama> (raw)
In-Reply-To: <55802EE1.6040703@dresearch-fe.de>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Tue, Jun 16, 2015 at 04:12:49PM +0200, Steffen Sledz wrote:
> For development purposes we use this method to build always from the HEAD revision of a git repository.
>
> -------------> snip <--------------
> SRCREV="${AUTOREV}"
> PV = "gitr${SRCPV}"
>
> SRC_URI = "git://git@bitbucket.org/.../foo.git;protocol=ssh"
> -------------> snap <--------------
>
> Now we like to do the same in one recipe which uses sources from two git repos.
>
> Our first try was this one. But if failed..
>
> -------------> snip <--------------
> SRCREV_foo="${AUTOREV_foo}"
> SRCREV_bar="${AUTOREV_bar}"
> PV = "gitr${SRCPV_foo}+${SRCPV_bar}"
>
> SRC_URI = " \
> git://git@bitbucket.org/.../foo.git;protocol=ssh,name=foo \
> git://git@bitbucket.org/.../bar.git;protocol=ssh,name=bar \
> "
> -------------> snap <--------------
>
> Is it possible to do what we want? And what's the right way to do it?
You need to set SRCREV_FORMAT variable.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] multiple git repos vs. AUTOREV?
Date: Tue, 16 Jun 2015 16:40:13 +0200 [thread overview]
Message-ID: <20150616144013.GC17938@jama> (raw)
In-Reply-To: <55802EE1.6040703@dresearch-fe.de>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Tue, Jun 16, 2015 at 04:12:49PM +0200, Steffen Sledz wrote:
> For development purposes we use this method to build always from the HEAD revision of a git repository.
>
> -------------> snip <--------------
> SRCREV="${AUTOREV}"
> PV = "gitr${SRCPV}"
>
> SRC_URI = "git://git@bitbucket.org/.../foo.git;protocol=ssh"
> -------------> snap <--------------
>
> Now we like to do the same in one recipe which uses sources from two git repos.
>
> Our first try was this one. But if failed..
>
> -------------> snip <--------------
> SRCREV_foo="${AUTOREV_foo}"
> SRCREV_bar="${AUTOREV_bar}"
> PV = "gitr${SRCPV_foo}+${SRCPV_bar}"
>
> SRC_URI = " \
> git://git@bitbucket.org/.../foo.git;protocol=ssh,name=foo \
> git://git@bitbucket.org/.../bar.git;protocol=ssh,name=bar \
> "
> -------------> snap <--------------
>
> Is it possible to do what we want? And what's the right way to do it?
You need to set SRCREV_FORMAT variable.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-06-16 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 14:12 multiple git repos vs. AUTOREV? Steffen Sledz
2015-06-16 14:20 ` [OE-core] " Paul Eggleton
2015-06-16 14:20 ` Paul Eggleton
2015-06-17 7:27 ` [OE-core] " Steffen Sledz
2015-06-17 7:27 ` Steffen Sledz
2015-06-17 8:10 ` [OE-core] " Richard Purdie
2015-06-17 8:10 ` Richard Purdie
2015-06-17 10:09 ` [OE-core] " Steffen Sledz
2015-06-17 10:09 ` Steffen Sledz
2015-06-17 10:25 ` [OE-core] " Steffen Sledz
2015-06-17 10:25 ` Steffen Sledz
2015-06-17 10:31 ` [OE-core] " Paul Eggleton
2015-06-17 10:31 ` Paul Eggleton
2015-06-16 14:40 ` Martin Jansa [this message]
2015-06-16 14:40 ` [oe] " Martin Jansa
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=20150616144013.GC17938@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.