WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [patch] Xen build - Debian vs Redhat layout patch option

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Bruce Edge <bruce.edge@xxxxxxxxx>
Subject: RE: [Xen-devel] [patch] Xen build - Debian vs Redhat layout patch options
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 16 Sep 2010 13:34:02 -0700 (PDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 16 Sep 2010 13:36:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <026d3c87-62f8-453b-8a53-f63eb9b44de6@default>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimi2-DzvysGnzJmEZtL4TXSsX6YDS0TPtoU-FiE@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1007071207480.17029@kaball-desktop> <AANLkTi=2TveuUANkar9d89k_Ck22RWFDEB-bKnCanOuz@xxxxxxxxxxxxxx> <19599.43888.826450.690087@xxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTik8b2evzTg8biVPVySvJTzVYmTSmSSt-WhbYrnD@xxxxxxxxxxxxxx> <19600.39408.486631.15438@xxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTim8TGttxjWiVCnXrh9wyzpfaC6sd=MirvYUw__y@xxxxxxxxxxxxxx> <19602.17927.197275.274485@xxxxxxxxxxxxxxxxxxxxxxxx 026d3c87-62f8-453b-8a53-f63eb9b44de6@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Um, OK, then what is the default going to be?  Or are you
> going to require everyone who uses ANY distro to edit a
> list of Config.mk parameters before the build does anything
> useful?  Seems to me if we group them as Bruce suggests and
> only require a single edit (or even do it automagically based
> on presence/contents of certain files), the vast majority
> of Xen developers will be better off.

Never mind, objection withdrawn.  With a reasonable default
and Bruce's distro_mapping.txt file that explains it (along
with a pointer to that file in Config.mk, I'm OK with it.

> -----Original Message-----
> From: Dan Magenheimer
> Sent: Thursday, September 16, 2010 2:24 PM
> To: Ian Jackson; Bruce Edge
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] [patch] Xen build - Debian vs Redhat layout
> patch options
> 
> > Bruce Edge writes ("Re: [Xen-devel] [patch] Xen build - Debian vs
> > Redhat layout patch options"):
> > > On Wed, Sep 15, 2010 at 3:03 AM, Ian Jackson
> > <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> > > > It is better to provide hooks to allow distros we don't know
> about
> > to
> > > > do what they want.
> > >
> > > You don't think there's any advantage to grouping all the distro
> > > directory dependencies in one place?
> >
> > No.  I think there is a disadvantage to grouping these kind of
> > configuration parameter settings by our idea of what distros there
> > are and how they work.
> 
> Um, OK, then what is the default going to be?  Or are you
> going to require everyone who uses ANY distro to edit a
> list of Config.mk parameters before the build does anything
> useful?  Seems to me if we group them as Bruce suggests and
> only require a single edit (or even do it automagically based
> on presence/contents of certain files), the vast majority
> of Xen developers will be better off.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel