From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Package Mirror Script
Date: Tue, 22 Oct 2013 15:10:11 +0200 [thread overview]
Message-ID: <20131022151011.715ec628@skate> (raw)
In-Reply-To: <20131021215849.GA3466@free.fr>
Dear Yann E. MORIN,
On Mon, 21 Oct 2013 22:58:49 +0100, Yann E. MORIN wrote:
> I'm afraid what you did is what is used to populate sources.b.o.
> There are no specific 'script' or procedure to do that.
>
> What are the gotchas you're bumped into?
>
> IIRC, there are a few isues yet with some host-packages that are nmot
> downloaded with 'make sources'. Is that your issue?. I think Thomas P.
> has a set od chages to fix this issue. Thomas?
True. As of today, the toolchain packages are not being handled by the
'make source' infrastructure, though I've already sent patches to fix
that.
Also, I think 'make allyespackageconfig' + 'make source' is inherently
broken: we have many Config.in "choice" statements, and depending on
the value of the choice, the tarballs to pull will not be the same
(packages supporting several versions, X.org big choice on KDrive vs.
full modular X.org, etc.), so there is in fact no way to simply pull
*all* possible tarballs. "make source" should guarantee you that it
downloads all the sources needed for your *current* configuration. But
there is no entirely full-proof way to download absolutely all possible
tarballs that Buildroot may need.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-22 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 19:15 [Buildroot] Buildroot Package Mirror Script Ryan Barnett
2013-10-21 21:58 ` Yann E. MORIN
2013-10-22 13:10 ` Thomas Petazzoni [this message]
2013-10-22 13:19 ` Ryan Barnett
2013-10-22 14:10 ` Thomas Petazzoni
2013-10-22 14:40 ` Ryan Barnett
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=20131022151011.715ec628@skate \
--to=thomas.petazzoni@free-electrons.com \
--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