Date: Thu, 24 Sep 2015 09:59:40 -0700 From: Jason Helfman <jgh@FreeBSD.org> To: Roman Bogorodskiy <bogorodskiy@gmail.com> Cc: Jason Helfman <jgh@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: virtualization ports Message-ID: <CAMuy=%2BhOciNbWFD9dqJPDMXNa0t4iWp8T5=JVRRcm5UYdomGyw@mail.gmail.com> In-Reply-To: <20150924073223.GA88752@dev.san.ru> References: <CAMuy=%2BjkutR5WkG6st_Ux6k2RxM=FbGCnYFtMFizJ-EaNZu8hQ@mail.gmail.com> <20150924073223.GA88752@dev.san.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 24, 2015 at 12:32 AM, Roman Bogorodskiy <bogorodskiy@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@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMuy=%2BhOciNbWFD9dqJPDMXNa0t4iWp8T5=JVRRcm5UYdomGyw>