Message-ID: <4C767306.4080108@redhat.com>
Date: Thu, 26 Aug 2010 07:58:30 -0600
From: Eric Blake <eblake@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100806 Fedora/3.1.2-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.2
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] NEW: {libtirpc/libtirpc1/libtirpc-devel}-0.2.1-1
References: <201008191720.o7JHKGoE008398@mx1.redhat.com> <4C6F1F4A.2030901@redhat.com> <4C6F26DA.2090009@cwilson.fastmail.fm> <20100821085401.GP11340@calimero.vinschen.de> <4C75E122.4070104@cwilson.fastmail.fm>
In-Reply-To: <4C75E122.4070104@cwilson.fastmail.fm>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 08/25/2010 09:36 PM, Charles Wilson wrote:
> Unless I rebuild with renamed versions, and bump the API number.
>
> Or, don't bump the API number and break stuff. Since it is a new
> package, and so far only Erick's private libvirt seems to use it, I'm
> actually leaning that way.
>
> Eric, any thoughts?

libtirpc is new enough, and I haven't distributed my built libvirt 
anywhere, that I would be just fine with a -2 without a new API number, 
if that makes life easier for you.  Ultimately, I do plan on doing an 
ITP for libvirt.  Right now, we don't really have any native VMs like 
qemu working under cygwin, and kvm is out of the question without access 
to the kernel; but a cygwin-built libvirt _is_ capable of doing remote 
control of VMs hosted on another machine.  But the ITP can wait until we 
are happy with the libtirpc situation.

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple