From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Name of downloaded archive, conflicts
Date: Mon, 28 Oct 2013 07:58:31 +0100 [thread overview]
Message-ID: <526E0B17.8020402@mind.be> (raw)
In-Reply-To: <20131025160524.4f8e922a@pcviktorin.fit.vutbr.cz>
On 25/10/13 16:05, Jan Viktorin wrote:
> Hello,
>
> I have encountred a problem when downloading custom kernel together
> with a custom (e.g.) u-boot. Both are downloaded from GitHub from a
> master branch. The URLs are (in case of using master branches):
>
> https://github.com/Xilinx/u-boot-xlnx/archive/master.tar.gz
> https://github.com/Xilinx/linux-xlnx/archive/master.tar.gz
>
> and that leads to a file name conflict in the dl/ directory. I end
> with linux kernel extracted in the u-boot build directory...
>
> Is there a way in buildroot how to specify a different name after
> download is done or another way how to avoid the conflict? I tried to
> google a bit, however, without a success.
This is a known issue, and we don't have a good solution for it.
We have considered prepending the package name to every archive that is
downloaded, but this has two important problems:
1. You can't use the download directory as a BR2_PRIMARY_SITE anymore.
2. If the same source is used by two packages (e.g. kernel-headers and
linux), then it will also be downloaded twice.
We haven't found a good solution for these problems. Ideas are welcome,
though.
Fortunately, for your use case, there's an easy solution. Don't use
'master', but instead use an explicit sha1 of the version you want to
download. Your .config should really be reproducible, so that you can
give it to a colleague and they'll build the _same_ kernel as you.
While you're developing linux and/or U-Boot, you can use the
_OVERRIDE_SRCDIR mechanism (which admittedly isn't very well documented
at the moment), which is a more explicit way of making 'local' changes to
the .config.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-10-28 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 14:05 [Buildroot] Name of downloaded archive, conflicts Jan Viktorin
2013-10-28 6:58 ` Arnout Vandecappelle [this message]
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=526E0B17.8020402@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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