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

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

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.

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).

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.

Wladimir

[-- Attachment #2: Type: text/html, Size: 1211 bytes --]

  reply	other threads:[~2014-04-03  5:52 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 [this message]
2014-04-03 16:01     ` devrandom

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='CA+s+GJDyNN=EWhhqCBvF+AL_2H2-78h+ffd21gZt+tybso8PPg@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=c1.sf-bitcoin@niftybox.net \
    /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