On Mon, Oct 7, 2024 at 1:53 PM Daniel P. Berrangé <berra...@redhat.com> wrote: > > Full CI enablement isn't a requirement until we want to turn on > > Rust by default. It would be sufficient to have a single job in > > CI using Fedora 40 that passes '--enable-rust' to demonstrate that > > this at least working on one platform we expect. > > I forgot to say that QEMU's 'refresh' script can customize the > dockerfiles from lcitool with an arbitrary amount of trailing > text - see the 'debian12_extras' for example.
Ok, I'll try to concoct something like that. > > If we want to actually build with the cutting edge, then I'd say > > it is sufficient to have a container based on Fedora rawhide, since > > that gives a heads up on what's soon to be impacting the next stable > > distro release, upto 6 months ahead of time - we don't need to be > > watching& debugging stuff that hasn't even been released by Rust > > yet IMHO. I think it's a good idea to give ourselves early access to lints, given that clippy and rustc are evolving more rapidly than C compilers (which already bite us every now and then). It tells us whether we consider them over-the-top and disable them, or potential bugs/traps that we want to fix now. Paolo
