From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v4] OSSTEST: introduce a raisin build test Date: Wed, 13 May 2015 10:01:23 +0100 Message-ID: <1431507683.8263.212.camel@citrix.com> References: <1431422408-16659-1-git-send-email-stefano.stabellini@eu.citrix.com> <1431425547.8263.127.camel@citrix.com> <1431430431.8263.143.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 Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, 2015-05-12 at 12:46 +0100, Stefano Stabellini wrote: > > Would a separate clone of the same raisin version with some sort of > > "dist" directory transported over be sufficient and supportable? Or are > > raisin's outputs not in one place and easily transportable? > > > > i.e. today build-$ARCH-libvirt picks up the dist.tar.gz files from the > > corresponding build-$ARCH, unpacks them and asks libvirt to build > > against that tree. > > Moving the dist directory over should work, although I have never tested > this configuration. Would you be willing to support this as a requirement going forward? I assume that it is not also necessary to reclone all the trees for the preexisting components, just the new ones? Ian.