From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 4/9] raisin: add a component to build qemu_traditional Date: Thu, 16 Apr 2015 11:59:24 +0100 Message-ID: <552F960C.4070302@eu.citrix.com> References: <1429110900-8286-4-git-send-email-stefano.stabellini@eu.citrix.com> <552E832A.9020900@citrix.com> <552E8870.6020302@citrix.com> <1429113529.15516.344.camel@citrix.com> <21806.36527.622876.472825@mariner.uk.xensource.com> <1429115186.25195.9.camel@citrix.com> <1429173926.25195.30.camel@citrix.com> <1429179039.25195.60.camel@citrix.com> <552F9179.7000109@eu.citrix.com> <1429181284.25195.68.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini , Ian Campbell Cc: Andrew Cooper , xen-devel@lists.xensource.com, Ian Jackson List-Id: xen-devel@lists.xenproject.org On 04/16/2015 11:55 AM, Stefano Stabellini wrote: > On Thu, 16 Apr 2015, Ian Campbell wrote: >> 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. > > That would also work, very simple solution to the problem. Or: "source defconfigs/4.5" in the main config file? -George