This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH][TOOLS] allow the selection of blktap and firmwar

To: Jeremy Katz <katzj@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH][TOOLS] allow the selection of blktap and firmware thru config files
From: Sean Dague <japh@xxxxxxxxxx>
Date: Thu, 10 Aug 2006 22:45:44 -0400
Cc: Julian Chesterfield <jac90@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 10 Aug 2006 19:46:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1155229080.6078.12.camel@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Jeremy Katz <katzj@xxxxxxxxxx>, Julian Chesterfield <jac90@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
References: <C0FFCDC1.B23%Keir.Fraser@xxxxxxxxxxxx> <DE24EEAA-AD81-4020-B33D-8A1FCEE2048E@xxxxxxxxxxxxxx> <bbac1dbb0f545972bc48b5fc90243b67@xxxxxxxxx> <E4B78A8F-208D-463F-9528-B0453EC6B081@xxxxxxxxxxxxxx> <b3475a08f730d416db157d8288429a5e@xxxxxxxxx> <1155229080.6078.12.camel@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Aug 10, 2006 at 12:58:00PM -0400, Jeremy Katz wrote:
> On Thu, 2006-08-10 at 14:51 +0100, Julian Chesterfield wrote:
> > Because libaio is often not included in the distro. In order to avoid 
> > breaking the build we either had to include checks in the Makefile for 
> > the existence of the library and build if necessary, or just statically 
> > build within the tree. We chose the latter since it was the cleanest 
> > approach.
> Except that for distributions, if there's a bugfix which needs to be
> applied to libaio, it now needs to go to two different places.  This is
> a path that is all but guaranteed to be a headache for distros in the
> future :(

Extremely concur.  All the extra security work that embedded libtiff and
libz caused over the past year or so should be plenty of reason to no embedd
a seperate copy of any library in a source tree.


Sean Dague
IBM Linux Technology Center                     email: japh@xxxxxxxxxx
Open Hypervisor Team                           alt: sldague@xxxxxxxxxx

Attachment: pgpJQ8UXsklG4.pgp
Description: PGP signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>