From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v4] OSSTEST: introduce a raisin build test Date: Mon, 18 May 2015 11:33:18 +0100 Message-ID: <1431945198.4944.30.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> <1431507683.8263.212.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: George Dunlap Cc: Ian Jackson , "xen-devel@lists.xen.org" , Wei Liu , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Mon, 2015-05-18 at 11:08 +0100, George Dunlap wrote: > On Wed, May 13, 2015 at 12:48 PM, Stefano Stabellini > wrote: > > On Wed, 13 May 2015, Ian Campbell wrote: > >> 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? > > > > Yeah, I think it is OK > > > >> I assume that it is not also necessary to reclone all the trees for the > >> preexisting components, just the new ones? > > > > Only if the user asks for a components to be built, the corresponding > > tree is cloned. > > Won't the problem here be disentangling the stuff installed in dist/ > (or whatever it's called) from the things we want to rebuild vs the > things we want to change? >>From the osstest PoV at least the proposal here only involves building additional things, not rebuilding anything which came from a previous build. e.g. given a build of xen.git now do a build of libvirt.git using those previously built Xen libs. But there is still the issue of separating stuff built in Pass-A from the stuff in Pass-B. Raisin could presumably have a concept of two dist dirs, dist.base and dist with the former being r/o. But that sounds to me like the sort of thing you wouldn't want in Raisin. Per component dist dirs is similarly surely possible but perhaps not something raisin wants. > I.e., ideally if you want to build just xen.git, you want dist/ to > contain the output of the previous build of seabios, qemut, qemuu, &c, > but *not* the output of previous xen.git builds (or, ideally, the > output of previous libvirt, pvgrub, or stubdom builds). Just tar and > untarr'ing dist/ after a full build won't accomplish that. > > Would it make sense to do some sort of "save snapshot" functionality > that would tar up the dist/ before building a particular component, > such that it could be used later? Sort of a "stage 2*" for raisin. > :-) > > -George > > * Referring to Gentoo. Not sure the comparison is 100% accurate.