← Back to team overview

kicad-developers team mailing list archive

Re: boost headers have been removed

 

On 06/06/2013 10:41 AM, Dick Hollenbeck wrote:
> 
> Hi Adam,
> 
> Although I am not a user of the PPA nor of pre-packaged downloads for KiCad, I would
> consider this offer to be a *very generous* one from you.   I think my fellow KiCad users
> would benefit from it.
> 
> 
> Is there any way we can have a substitute plan, on the shelf, should you ever lose
> interest in providing this service?  Maybe a copy of some scripts or current PPA work,
> whatever would make the task easiest?
> 
> 
> 
> On the problem at hand, I download the tar.bz2 file using wget at the command line, and
> the sourceforge download started out at only 8 K/sec and went up from there.  It took me
> 14 minutes plus to do the download.  The computed hash in the PPA logs is
> 
> d41d8cd98f00b204e9800998ecf8427e
> 
> and I find that this is the same you get on an empty file:
> 
> $ touch empty.file
> $ md5sum empty.file
> 
> d41d8cd98f00b204e9800998ecf8427e
> 
> 
> So the launchpad site may actually be blocking the download with a firewall rule or such.
> A TIMEOUT setting change is barely worth the try.
> 
> 
> As an experiment, I pushed the tar.bz2 file into its own bzr repo and pushed that to kicad
> project.  (Please do not tell launchpad folks.)  This exposes then an http URL at
> 
> 
> http://bazaar.launchpad.net/~kicad-testing-committers/kicad/boost/download/head:/boost_1_53_0.tar.bz2-20130606145758-00fag66fz00gstq5-1/boost_1_53_0.tar.bz2
> 
> 
> I then did wget against that URL, suddenly my rural internet connection became the
> bottleneck, as you would expect.  So launchpad did well.  The download only took 6 plus
> minutes.
> 
> 
> So some choices are available to you Adam.  As I said below, if you stuff the tar.bz2 file
> into the .downloads-by-cmake dir in advance of the first build, the download step will be
> skipped.  We can also use the launchpad URL, but that seems unnatural to me, and self
> defeating relative to the original idea of ease of upgrading boost.
> 
> 
> To fix the PPA using the services there, rather than your build cluster, it seems
> pre-loading the boost tar.bz2 file is necessary, because we/I suspect a firewall rule
> blocking the download.

And we'd either have to supply CMake 2.8.4 for Lucid build, or relax that requirement in
the topmost CMakeLists.txt down to 2.8.0.




References