On Tue, 2020-05-05 at 15:51 +0100, Daniel P. Berrangé wrote: > On Tue, May 05, 2020 at 04:33:48PM +0200, Andrea Bolognani wrote: > > On Tue, 2020-05-05 at 14:49 +0100, Daniel P. Berrangé wrote: > > > That's only required for VM builds, and would use of the "all" > > > wildcard when building VMs, so I'm not wanting to do that, as I > > > won't have tested anything related to VMs. > > > > It also serves as documentation for our expectations when it comes to > > which project can be built on which platform, and was intended to > > prevent the use of > > > > ./lctiool $action $target $project > > > > when $target is known not to support $project, even though we didn't > > enfore that for 'update' and 'build' in order to make > > > > ./lcitool $action all all > > > > work smoothly, and 'dockerfile' lost the check in one of your > > recent patches... > > IIUC, "lcitool build libvirt-fedora-32 all" will try to build all > projects in the host's inventory. So if we add libvirt-rust, to the host > inventory we need to full the full VM setup for the project, otherwise > we'll break this build. Mh, that's correct. Another consequence of not really having planned for things to be introduced only partially. -- Andrea Bolognani / Red Hat / Virtualization
