From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Package Mirror Script
Date: Tue, 22 Oct 2013 16:10:48 +0200 [thread overview]
Message-ID: <20131022161048.2e23aed8@skate> (raw)
In-Reply-To: <OF1B2465A6.AABEECD2-ON86257C0C.0048E870-86257C0C.004924DF@rockwellcollins.com>
Dear Ryan Barnett,
On Tue, 22 Oct 2013 08:19:12 -0500, Ryan Barnett wrote:
> > 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.
>
> Thanks for the information, I was hoping there was some magic that was
> being done for the buildroot mirror that I was missing. I guess we will
> just have to maintain an 'allyespackageconfig' that fixes all of the
> gotchas.
It'd be nice though if you could give details about what those
"gotchas" are, so we can see if they are gotchas that should be fixed,
or inherent limitations of the Buildroot design.
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 14: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
2013-10-22 13:19 ` Ryan Barnett
2013-10-22 14:10 ` Thomas Petazzoni [this message]
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=20131022161048.2e23aed8@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