[Buildroot] Buildroot Package Mirror Script

Ryan Barnett rjbarnet at rockwellcollins.com
Tue Oct 22 13:19:12 UTC 2013


Thomas P, Yann, 

Thomas Petazzoni <thomas.petazzoni at free-electrons.com> wrote on 10/22/2013 
08:10:11 AM:

> 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.
 
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.

Thanks,
-Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131022/89057264/attachment.html>


More information about the buildroot mailing list