Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of niftybox.net
	designates 95.142.167.147 as permitted sender)
	client-ip=95.142.167.147;
	envelope-from=c1.sf-bitcoin@niftybox.net; helo=i3.hyper.to; 
Message-ID: <1396540918.13415.78.camel@mimiz>
From: devrandom <c1.sf-bitcoin@niftybox.net>
To: Wladimir <laanwj@gmail.com>
Date: Thu, 03 Apr 2014 09:01:58 -0700
In-Reply-To: <CA+s+GJDyNN=EWhhqCBvF+AL_2H2-78h+ffd21gZt+tybso8PPg@mail.gmail.com>
References: <CA+s+GJDJRW-ydQ-93dHLShZoWtCox=J47TGO=wwSq7Ahn0LwMw@mail.gmail.com>
	<1396500468.13415.71.camel@mimiz>
	<CA+s+GJDyNN=EWhhqCBvF+AL_2H2-78h+ffd21gZt+tybso8PPg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Detailed gitian build guide
Precedence: list

On Thu, 2014-04-03 at 07:51 +0200, Wladimir wrote:
> 
> On Thu, Apr 3, 2014 at 6:47 AM, devrandom <c1.sf-bitcoin@niftybox.net>
> wrote:
>         Nice!
>         
>         I wonder how much of this could be scripted.
> 
> 
> Everything, probably, using vmbuilder (and/or vagrant as Nick Simpson
> suggests). But that's not the point here. It is to provide exact steps
> that people can follow to get a basic (virtual) machine that they can
> use to do gitian builds.

Understood.
> 
> I didn't want to end up with a
> gitian-builder-that-builds-a-gitian-builder :-) The host machine may
> not even have any scripting languages installed (in the case of
> Windows).

Yes, I can see the turtles there.
> 
> 
> It may be possible to script *some* parts (most of the quoted bash
> script is runnable as script) without automating the entire process,
> but I hope that over time we can make Gitian itself easier to
> use/setup, so that less steps are needed in the first place.

Understood. :)  I would definitely like to see in Gitian any
improvements that make it easier for newcomers to get started.
> 
> 
> Wladimir
> 
> 
> 

-- 
Miron / devrandom