> > After discussion on the list and IRC I decided to go with a solution based > purely on Travis as this has the least moving pieces and external > dependencies[3]. > > For each build, packages are built as individual build jobs using the > build matrix feature of Travis. The list of packages to build is specified > in the env: section of .travis.yml. > > Btw - is there something which needs
sudo: required in the Travis builds (rather than sudo: false) ?
