Re: [Xen-devel] [PATCH 4/9] raisin: add a component to build qemu_traditional

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2015-04-16 at 11:39 +0100, George Dunlap wrote:
> On 04/16/2015 11:25 AM, Stefano Stabellini wrote:
> > Each component is independent and there is no knowledge about versions
> > of one component (xen 4.5 and earlier) needing one or more versions of
> > another component (qemu-traditional).  The main idea was that the
> > versions or tags would be supplied by the user. Maybe there should be?
> > That would increase the complexity though.
> 
> Well I thought the main idea actually was that the user just tweaks a
> few settings, types "./raise fullauto" and everything Just Works? :-)
> 
> In which case, having a RELEASE macro (or RELEASE_DEFAULTS?) you could
> set to 4.5, 4.6, or unstable seems like the best interface, and which
> you could then override with your own branches if you wanted to, would
> be the best interface.
> 
> That is, unless we want to have something like "git checkout
> release/4.5". :-)

I had been assuming it was either that or "cp 4.5_defconfig config"
or ./raise 4.5_defconfig etc.

> 
> > I am starting to agree with George that supporting only 4.6+ would be a
> > decent place to start :-)
> 
> I think focusing on getting raise and the various Xen trees the way we
> want them ideally is a good start.  We can't make major changes to 4.5,
> so there's no real time constraint to adding the functionality into
> raisin.  (But we should make sure the interface isn't too difficult to
> integrate with.)
> 
>  -George
> 



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