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

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

> 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