virtualization ports

Jason Helfman jgh at FreeBSD.org
Thu Sep 24 16:59:48 UTC 2015


On Thu, Sep 24, 2015 at 12:32 AM, Roman Bogorodskiy <bogorodskiy at gmail.com>
wrote:

>   Jason Helfman wrote:
>
> > I have a number of ports that I maintain, that I really never use but at
> > one time I did. Initially, I put them into the portstree to help out the
> > community, with the idea that I would be using them one day, however I
> work
> > at a VMware shop, and the likelihood of me using this software is looking
> > far less likely. I was wondering if it would be okay to assign these
> ports
> > to virtualization group?
> >
> > deskutils/virt-manager
> > devel/libvirt
> > devel/libvirt-glib
> > devel/libvirt-java
> > devel/py-libvirt
> > devel/spice-protocol
> > net-mgmt/virt-viewer
>
> FWIW, I could take care of libvirt, py-libvirt, libvirt-glib and
> virt-manager.
>
> Roman Bogorodskiy
>
>
Sounds good, thanks! Additionally, if you are going to take virt-manager,
you really should take spice-protocol and virt-viewer as they are
dependencies and require updates for virt-manager.
Thoughts?

-jgh

-- 
Jason Helfman          | FreeBSD Committer
jgh at FreeBSD.org     | http://people.freebsd.org/~jgh  | The Power to Serve


More information about the freebsd-virtualization mailing list