From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [xen-unstable bisection] complete build-i386-libvirt
Date: Tue, 1 Jul 2014 11:07:46 +0200
Message-ID: <1404205666.8515.194.camel@Solace>
References: <E1X1J0P-0002Dl-FF@osstest.cam.xci-test.com>
	<1404112287.1829.96.camel@dagon.hellion.org.uk>
	<21425.28790.529605.216581@mariner.uk.xensource.com>
	<1404138350.19744.9.camel@kazak.uk.xensource.com>
	<21425.30200.419334.437090@mariner.uk.xensource.com>
	<1404140685.7116.16.camel@kazak.uk.xensource.com>
	<21425.32899.875481.702646@mariner.uk.xensource.com>
	<1404202146.1829.122.camel@dagon.hellion.org.uk>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3031036703705815067=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1404202146.1829.122.camel@dagon.hellion.org.uk>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jim Fehlig <jfehlig@suse.com>, xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

--===============3031036703705815067==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-+0RF0rnP5ejqOhxLIkn1"

--=-+0RF0rnP5ejqOhxLIkn1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On mar, 2014-07-01 at 09:09 +0100, Ian Campbell wrote:
> On Mon, 2014-06-30 at 16:21 +0100, Ian Jackson wrote:
> > Ian Campbell writes ("Re: [Xen-devel] [xen-unstable bisection] complete=
 build-i386-libvirt"):
> > > Oh wait. If libvirt supports up to e.g. Xen 4.4 today then this optio=
n
> > > would cause it to #define LIBXL_API_VERSION to that. But Xen 4.2 and =
4.3
> > > libxl wouldn't know what to do with it and would bail out.
> >=20
> > Yes.
> >=20
> > > We could deploy this flag only on the xen-unstable flights on the
> > > assumption that this is the only place where the libxl API ought to b=
e
> > > changing.
> >=20
> > Indeed.

> We could make the build-*-libvirt jobs build twice, once with and once
> without. Perhaps in the libvirt flight only. Would that work?
>=20
+1

If going for the LIBXL_API_VERSION compile option way, I like this idea
of building twice a lot.

It avoids unnecessarily holding a push but, at the same time, let us
know libvirt requires attention. It means a bit more of time, but not
that much, I think.

Dario

--=20
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


--=-+0RF0rnP5ejqOhxLIkn1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlOyemIACgkQk4XaBE3IOsTM4QCfShgJu5oiiTr2wXfdJ0H7vvrY
IWcAni0l47jZoiYwQZG0XN8H7pvGDOHC
=141T
-----END PGP SIGNATURE-----

--=-+0RF0rnP5ejqOhxLIkn1--


--===============3031036703705815067==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============3031036703705815067==--