From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 22 Oct 2013 15:10:11 +0200 Subject: [Buildroot] Buildroot Package Mirror Script In-Reply-To: <20131021215849.GA3466@free.fr> References: <20131021215849.GA3466@free.fr> Message-ID: <20131022151011.715ec628@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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