From: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
To: openembedded-core@lists.openembedded.org
Subject: Two recipes with the same file name for the SRC_URI
Date: Fri, 01 Feb 2013 10:35:14 +0100 [thread overview]
Message-ID: <510B8C52.4020700@oss.bmw-carit.de> (raw)
Hi all,
I ran into the following issue with bitbake:
I have two recipes, where the SRC_URI of both recipes have the same file
name (but of course, different URLs), e.g. SRC_URI =
"http://foo.com/src.tar.gz" and SRC_URI = "http://bar.com/src.tar.gz".
Now when I want to fetch both of them, bitbake does not download both of
them because they have the same name, and it assumes the file is already
downloaded if one of the files is downloaded.
Is there an option to set the local file name after downloading in the
recipe? The OpenEmbedded Manual does not mention any.
Or is there another way to solve the problem? Using Google and searching
through the manual did not help me.
Lukas
next reply other threads:[~2013-02-01 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 9:35 Lukas Bulwahn [this message]
2013-02-01 10:32 ` Two recipes with the same file name for the SRC_URI Burton, Ross
2013-02-01 13:49 ` Lukas Bulwahn
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=510B8C52.4020700@oss.bmw-carit.de \
--to=lukas.bulwahn@oss.bmw-carit.de \
--cc=openembedded-core@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