Date: Thu, 24 Sep 2015 10:32:25 +0300 From: Roman Bogorodskiy <bogorodskiy@gmail.com> To: Jason Helfman <jgh@FreeBSD.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: virtualization ports Message-ID: <20150924073223.GA88752@dev.san.ru> In-Reply-To: <CAMuy=%2BjkutR5WkG6st_Ux6k2RxM=FbGCnYFtMFizJ-EaNZu8hQ@mail.gmail.com> References: <CAMuy=%2BjkutR5WkG6st_Ux6k2RxM=FbGCnYFtMFizJ-EaNZu8hQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150924073223.GA88752>