public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: devrandom <c1.sf-bitcoin@niftybox.net>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Detailed gitian build guide
Date: Thu, 03 Apr 2014 09:01:58 -0700	[thread overview]
Message-ID: <1396540918.13415.78.camel@mimiz> (raw)
In-Reply-To: <CA+s+GJDyNN=EWhhqCBvF+AL_2H2-78h+ffd21gZt+tybso8PPg@mail.gmail.com>

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






      reply	other threads:[~2014-04-03 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 12:27 [Bitcoin-development] Detailed gitian build guide Wladimir
2014-04-03  4:47 ` devrandom
2014-04-03  5:51   ` Wladimir
2014-04-03 16:01     ` devrandom [this message]

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=1396540918.13415.78.camel@mimiz \
    --to=c1.sf-bitcoin@niftybox.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=laanwj@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox