Philippe Mathieu-Daudé <f4...@amsat.org> writes: > On 07/25/2017 11:15 AM, Alex Bennée wrote: >>> +++ b/tests/docker/dockerfiles/debian-bleeding-dev.docker >>> @@ -0,0 +1,94 @@ >>> +# >>> +# Docker x86_64 bleeding image >>> +# >>> +# This docker target builds on the debian unstable base image. Further >>> +# libraries which are not widely available are installed by hand. >>> +# >> >> Not for 2.10 please. > > Surely not ;) Also unlikely to get merged in mainline... > > [...] >> There are a lot of moving parts basing this in debian unstable and >> compiling extra bleeding edge stuff. What does this buy that the clang >> and toolchain builds in Travis don't already cover? > > Bleeding is bleeding :) This is an implicit No Warranty clause... > It might trigger something useful or give you slow death. > > https://wiki.debian.org/DebianUnstable > "If you are a hardcore developer or tester you should use this release." > > https://www.debian.org/doc/manuals/securing-debian-howto/ch10.en.html#s10.1.3 > "you should not use Debian's unstable branch for production-level systems"
Quite but from a QEMU point of view these are being used for CI loops and proving a known state of something for users to test on. As I said in reply elsewhere I think to get the benefit of recent Clang and GCCs it would be best to base of some sort of stable base. -- Alex Bennée
