On Thu, May 09, 2019 at 10:40:51AM +0200, Ján Tomko wrote: > On Thu, May 09, 2019 at 10:30:25AM +0200, Andrea Bolognani wrote: > > On Wed, 2019-05-08 at 17:29 +0100, Daniel P. Berrangé wrote: > > > On Wed, May 08, 2019 at 06:21:21PM +0200, Olaf Hering wrote: > > > > On Wed, Apr 03, Ján Tomko wrote: > > > > > > > > > Since all our supported platforms include at least yajl 2.0.4, > > > > > use pkg-config to detect the library and set the minimum to 2.0.3. > > > > > > > > In case SLE_12 is on the list of supported platforms, this kicked it > > > > off of the list. SLE_12 (and Leap 42.3) comes with version 2.0.1. > > > > SLE_15 has version 2.1.0. > > Oops, so 'Leap 42.3' is the one I should be looking at to see what's in > SLE_12? > https://repology.org/project/yajl/versions Yes, there's an explanation of the versioning scheme here: https://lists.opensuse.org/opensuse-project/2017-04/msg00014.html openSUSE Leap 42.3 is eqiuv to SLE 12 sp3 So we can use Leap versions in repoology to track requirements for SLE, which I didn't realize was possible in the past. 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 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
