On Wed, 2019-09-18 at 17:46 +0100, Daniel P. Berrangé wrote: > On Wed, Sep 18, 2019 at 02:55:53PM +0200, Andrea Bolognani wrote: > > So, to be clear, you're advocating for keeping our list of target > > platforms unchanged and exempt Meson specifically from the implicit > > requirement we've had so far, which is that all build dependencies > > should be installed from distro-provided packages? > > > > I'm not saying that I'm against this, but I think we should at the > > very least document this prominently, and ideally get an explicit > > thumbs up from a few downstreams because this could negatively > > affect their ability to package new libvirt versions. > > Of course the best is if the distro's already ships a standard > meson that's good enough, if they don't though, they need to > use a custom meson to build libvirt. So the comparison is > > - libvirt.tar.gz that contains a copy of meson sources > - libvirt.tar.gz and a meson.tar.gz > > Both these cases are functionally the same in what the distro > ends up building & bundling. So if one causes policy problems > for the distro, the other will too IMHO. Sounds reasonable to me, but I would really like to have ACKs from at least a couple of downstreams and ideally a PoC showing that doing this doesn't create a massive amount of pain for them. And documenting it is definitely a must. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
