On Friday, 04.03.2016 at 17:05, Antti Kantee wrote: > On 04/03/16 17:01, Martin Lucina wrote: > >>>IMHO the best thing to do would be to eventually change to a Dockerized > >>>build with one "build container" per package, that way at least anyone with > >>>Docker installed can replicate a build locally (or anywhere with Docker). > >>>The reason I've not done that yet is because I wanted something that works > >>>ASAP and doesn't depend on anything except Travis. > >> > >>Depending on Docker is a no-no, just like pushing for any other > >>non-universally available host features. > > > >Sorry, I wasn't clear. I don't mean "make the packages build depend on > >Docker". I mean "make the *Travis* build depend on Docker". That way, > >anyone could replicate the exact same build locally when testing, and do so > >at their leisure without having to wait for Travis. That seems like an > >advantage to me. > > Ok. > > Ideally, one would never have to replicate the Travis env, but that's > probably fantansyland stuff, even if we can improve the status quo.
Exactly. If we build on Travis in Docker containers then we control the build environment since the container can use Debian stable/testing/whatever userland we like to build on. So we don't need to deal with anything Travis-specific.
