Re: libvirt status with Xen (netbsd 6.1.2 amd64) ?

[Alistair Crooks <agc%pkgsrc.org@localhost>]

On Fri, May 30, 2014 at 06:57:25PM -0500, Eric Schnoebelen wrote:
> giannidaprile writes:
> - libvirt is compiled with only qemu backend by default.  Pkgsrc doesn't
> - currently have any buildlink glue for xen so this is not trivial.  Sure
> - would be nice to have.
> 
> I took a wag at doing this a week or so ago.  It turns out the
> xen hypervisor interfaces in the libvirt edition in pkgsrc have
> more linux-ism's and other strangeness to keep the patches
> reasonable.  The xen hypervisor interface could be re-written
> using solely xen API calls (through libxc) and it would be much
> cleaner and easier to maintain.  However, I didn't feel like
> refactoring the entire source file as a patch, so it's going
> back onto the back burner.
> 
> However, I did make up a patch that can be applied to the pkgsrc
> tree to allow someone else to try and wack this into shape.

Thanks for that, much appreciated.

I haven't added it to the libvert pkgsrc entry (yet), mainly because
libvirt tends to be the package I am most often notified has a security
vulnerability, and bringing patches forward, in those circumstances, can
be a real pain.

Having said that, I'd like to get this into our package. Do I split
the package into 2, a libvirt and a libvirt-devel? Or bite the bullet
and bring forward changes whenever we need to upgrade? Or... some
other suggestion?

Thanks,
Alistair