From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v4] OSSTEST: introduce a raisin build test
Date: Wed, 13 May 2015 10:01:23 +0100 [thread overview]
Message-ID: <1431507683.8263.212.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505121243010.20496@kaball.uk.xensource.com>
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.
next prev parent reply other threads:[~2015-05-13 9:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 9:20 [PATCH v4] OSSTEST: introduce a raisin build test Stefano Stabellini
2015-05-12 10:12 ` Ian Campbell
2015-05-12 11:16 ` Ian Jackson
2015-05-12 11:20 ` Stefano Stabellini
2015-05-12 11:33 ` Ian Campbell
2015-05-12 11:46 ` Stefano Stabellini
2015-05-13 9:01 ` Ian Campbell [this message]
2015-05-13 11:48 ` Stefano Stabellini
2015-05-13 11:57 ` Ian Campbell
2015-05-18 10:08 ` George Dunlap
2015-05-18 10:33 ` Ian Campbell
2015-05-18 10:54 ` George Dunlap
2015-05-18 11:21 ` Ian Campbell
2015-05-18 13:05 ` George Dunlap
2015-05-18 13:14 ` Ian Campbell
2015-05-18 13:23 ` George Dunlap
2015-05-18 13:32 ` Ian Campbell
2015-05-18 13:33 ` Ian Jackson
2015-05-18 13:46 ` Ian Campbell
2015-06-17 14:13 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431507683.8263.212.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.