From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [ANNOUNCE] Project Raisin Date: Thu, 2 Apr 2015 10:09:10 +0100 Message-ID: <1427965750.4037.10.camel@citrix.com> References: 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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, 2015-03-31 at 11:16 +0100, Stefano Stabellini wrote: > Hi all, > > A few weeks ago I started hacking on a new project, consisting in a set > of bash scripts to build xen-unstable and a few other useful elements. > It is still in very early stages. > > The name of the new project is "Raisin", from Raise Xen, pun intended > ;-) > It is a bit like DevStack[1] for Xen: its purpose is to simply and > quickly retrieve and build Xen and any other related components from > source, such as Libvirt and Grub2. I think this is great and I look forward to it being integrated with osstest so we can start moving 3rd party components out of xen.git >>From a UI point of view I think it would be useful to move as much non-user-facing stuff as possible into a subdirectory such that a user just gets something like: $ ls README raisin.sh* lib components COPYING config rather than being overwhelmed by all sorts of scripts etc. I see you've moved the components into a subdir since the first posting. which is good, I'd suggest to move as much of the other stuff (common-funcitons, git-checkout, mk*) down a level too. Ian.