[PATCH v1] meson: fix xenstore and xentoollog detection

Daniel P. Berrangé berrange at redhat.com
Mon Jun 14 13:38:19 UTC 2021


On Mon, Jun 14, 2021 at 03:24:03PM +0200, Olaf Hering wrote:
> Am Mon, 14 Jun 2021 11:06:51 +0100
> schrieb Daniel P. Berrangé <berrange at redhat.com>:
> 
> > Repology reports the following
> 
> Is it expected that people replace just "libvirt" on a system, and leave everything as it is?
> 
> If I would build a Xen server, the obvious change is to also replace Xen with the variant I want or need.
> 
> Well, and that is exactly what I do. For testing I have to run old
> variants of it, and I expect that libvirt can deal with it. Right
> now it does. I will be really disappointed if the base line is bumped
> for no good reason. "cc.find_library" has to be supported for other
> libraries anyway, so there is no downside to use it if "dependency"
> can not be used. How much libxl code could be removed, no idea.
> Without looking I say its likely not worth.

None of these questions generally have clear cut answers.

Thus libvirt follows the same policy as QEMU for supporting platforms,
in that we'll aim to support the 2 most recent releases of any major
OS distro. This gives a clear rule for how we decide the minimum
version of any package, with results that are consistent across
the whole distro package set. eg there's no point keeping Xen
support for an old distro if we've dropped support for the GCC /
GLib2 version on that same distro, and vica-verca.

Based on this policy, it is clear that the Xen minimum should be
4.9 based on version information we can see for the distros.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|




More information about the libvir-list mailing list