Open rod-glover opened 7 years ago
Mmmmm, packaging is something that I don't necessarily want to get into, if we can avoid it... especially for GDAL (which is a challenging build to maintain). FWIW, there is a 2.x build for Ubuntu, but it's deps are probably substantial.
I realize that 10 minutes is a long time to wait for a test to run, but Travis is kind of the line of last defence. We should be running our tests locally anyway, and for that we don't need to build GDAL every time.
So overall my thoughts are we should speed up the build if it's easy to do, but maintaining our own PPA of GDAL 2.x is over the easy threshold IMO.
Thought you might say that. I wasn't sure how hard packaging is.
The test run delay is only onerous if you've introduced problems into the .travis.yml file and are debugging it ... which I was :)
Just for the record, this issue has been driving me crazy all day. Maybe we don't have to go so far as setting up a PPA... the build process is fairly straightforward and repeatable. Maybe we could tar up the results of the "make install", put them in a public URL, and then download them + "tar -C" to do a quick install?
It used to be a 10 minute build and now it's more like 20-30... zzzzzzzzzzzzzzzz.
This has been driving us nuts (and wasting time) for three years now. Let's fix it.
It takes Travis > 10 min to create the build. The vast majority of the time is taken up by the installation of GDAL 2.0.2, which does not have a prepackaged Ubuntu apt-get install for it (only GDAL 1.11.3 does).
Suggest we create our own GDAL 2.x package for Ubuntu. We can publish it to a PPA if we don't want to jump the hoops to have it included in the public Ubuntu offerings.