> > 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. > > That would be ideal. I mean to get round to helping out, with a view to publishing the artefact binaries automatically. Did you make any progress with putting the builds into a Docker container?
- Travis CI builds for rumprun-packages available Martin Lucina
- Re: Travis CI builds for rumprun-packages available Antti Kantee
- Re: Travis CI builds for rumprun-packages available Martin Lucina
- Re: Travis CI builds for rumprun-packages avail... Antti Kantee
- Re: Travis CI builds for rumprun-packages a... Martin Lucina
- Re: Travis CI builds for rumprun-packa... Antti Kantee
- Re: Travis CI builds for rumprun-p... Martin Lucina
- Re: Travis CI builds for rumpr... David Halls
- Re: Travis CI builds for rumpr... Martin Lucina
- Re: Travis CI builds for rumprun-packages available David Halls
- Re: Travis CI builds for rumprun-packages available Martin Lucina
- Re: Travis CI builds for rumprun-packages avail... David Halls
- Re: Travis CI builds for rumprun-packages a... Martin Lucina
- Re: Travis CI builds for rumprun-packa... David Halls
- Re: Travis CI builds for rumprun-p... David Halls
- Re: Travis CI builds for rumpr... David Halls
- Re: Travis CI builds for rumpr... David Halls
- Re: Travis CI builds for rumpr... Antti Kantee
