From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: multiple git repos vs. AUTOREV?
Date: Tue, 16 Jun 2015 16:12:49 +0200 [thread overview]
Message-ID: <55802EE1.6040703@dresearch-fe.de> (raw)
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?
Thx,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next reply other threads:[~2015-06-16 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 14:12 Steffen Sledz [this message]
2015-06-16 14:20 ` multiple git repos vs. AUTOREV? Paul Eggleton
2015-06-17 7:27 ` Steffen Sledz
2015-06-17 8:10 ` Richard Purdie
2015-06-17 10:09 ` Steffen Sledz
2015-06-17 10:25 ` Steffen Sledz
2015-06-17 10:31 ` Paul Eggleton
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=55802EE1.6040703@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox