Re: virtualization ports

2015-09-29 Thread Jason Helfman
On Mon, Sep 28, 2015 at 9:50 AM, Roman Bogorodskiy 
wrote:

>   Jason Helfman wrote:
>
> > On Thu, Sep 24, 2015 at 12:32 AM, Roman Bogorodskiy <
> bogorods...@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?
>
> Yes, it looks reasonable.
>
> Roman Bogorodskiy
>

Thanks.

I'll take care of this, then.

-jgh

-- 
Jason Helfman  | FreeBSD Committer
j...@freebsd.org | http://people.freebsd.org/~jgh  | The Power to Serve
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: virtualization ports

2015-09-28 Thread Roman Bogorodskiy
  Jason Helfman wrote:

> On Thu, Sep 24, 2015 at 12:32 AM, Roman Bogorodskiy 
> 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?

Yes, it looks reasonable.

Roman Bogorodskiy


pgp3l_WEY6j5a.pgp
Description: PGP signature


Re: virtualization ports

2015-09-24 Thread Jason Helfman
On Thu, Sep 24, 2015 at 12:32 AM, Roman Bogorodskiy 
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
j...@freebsd.org | http://people.freebsd.org/~jgh  | The Power to Serve
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: virtualization ports

2015-09-24 Thread Roman Bogorodskiy
  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
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"