On Wed, Jul 08, 2015 at 03:37:43PM +0100, Zeeshan Ali (Khattak) wrote: > >> Also keeping in mind that it makes very little > >> sense to upgrade libvirt-glib and not libvirt since libvirt doesn't > >> break any ABI/API. > > > > Generally speaking, there could be security issues, critical bugs in > > Boxes which require a libvirt-glib update to be fixed, > > That is why we roll out bug fix releases to stable releases and try > our best not to bump any deps while doing so. So far, we haven't done that for libvirt-glib, just incremental releases with bugfixes and new features... > > ... where > > upgrading just libvirt-glib would be much more convenient than upgrading > > the whole stack. So all in all, this is just a tradeoff to make between > > making our life easier, and (potentially) making distributions life easier. > > Surely we need to meet somewhere in between. If Ubuntu or Debian would > for example not upgrade their libvirt for many years to come, would we > keep wasting our time on adding ugly hacks upstream for them? So far, you keep saying "let's bump the req!", but you haven't brought anything forward to support that "ugly hack" statement in this specific case, nor any hard data regarding which distros could be impacted by a req bump. I'll stop this discussion until you bring some concrete datapoints to the table. Christophe
Attachment:
pgpIFbjWbIWI8.pgp
Description: PGP signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list