On Thu, Dec 03, 2009 at 03:41:08PM +0100, Paolo Bonzini wrote: > On 12/03/2009 01:11 PM, Daniel Veillard wrote: > > hum ... that becomes an external library, one more dependancy > >on the other hand we don't have to track bug fixes.... > > What about using submodules + static linking of libyajl? That would fix > the "dependency" part and make bug tracking a bit harder. That won't fly with Fedora packaging rules which have a strict policy on not allowing use of any bundled 3rd party source. Even if upstream project ships it, Fedora will require that it is packaged & maintained as a separate package. It is not hard to build & package YAJL, since it is a tiny library with no tricky dependancies to satisfy, so I'm going to package it for Fedora. Other distros can have the choice of packaging it separately too, or just including it directly in their libvirt packages as per their own policies. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list