[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v9 5/6] Clone and build Seabios by default
Ian Campbell writes ("Re: [Xen-devel] [PATCH v9 5/6] Clone and build Seabios by default"): > Unfortunately I expect that distros will want to package qemu once (from > upstream) with support for all the various options, including Xen, > enabled and depend on that in their Xen packaging rather than packaging > a slightly different qemu a second time. Quite. > I'm not sure how we can address this without exploding our test matrix. > It seems like we need to test at a minimum the current qemu stable and > development branches :-/ This is no different to the kernel, of course. We don't do a very good job of testing different upstream kernels but it's on my todo list. > > I don't have an opinion on seabios because I am nore sure how many > > changes are we going to make to it. However I recall that you and/or > > IanC were in favor of having or own branch of seabios as well. > > I think that even if we never diverge from upstream and irrespective of > whether we stick in lockstep or not we should host a tree to point our > users (and default build) at. This gives us flexibility if we ever do > need to diverge and also isolates our users from issues with 3rd party > servers. Indeed so. But should it be one tree for each Xen branch, and does it need a push gate ? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |