1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WVaZG-00023E-06
for bitcoin-development@lists.sourceforge.net;
Thu, 03 Apr 2014 05:52:02 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.180 as permitted sender)
client-ip=209.85.213.180; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f180.google.com;
Received: from mail-ig0-f180.google.com ([209.85.213.180])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WVaZF-0005pO-7V
for bitcoin-development@lists.sourceforge.net;
Thu, 03 Apr 2014 05:52:01 +0000
Received: by mail-ig0-f180.google.com with SMTP id c1so1355782igq.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 02 Apr 2014 22:51:56 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.60.103 with SMTP id g7mr13476771igr.20.1396504315937;
Wed, 02 Apr 2014 22:51:55 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Wed, 2 Apr 2014 22:51:55 -0700 (PDT)
In-Reply-To: <1396500468.13415.71.camel@mimiz>
References: <CA+s+GJDJRW-ydQ-93dHLShZoWtCox=J47TGO=wwSq7Ahn0LwMw@mail.gmail.com>
<1396500468.13415.71.camel@mimiz>
Date: Thu, 3 Apr 2014 07:51:55 +0200
Message-ID: <CA+s+GJDyNN=EWhhqCBvF+AL_2H2-78h+ffd21gZt+tybso8PPg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: devrandom <c1.sf-bitcoin@niftybox.net>
Content-Type: multipart/alternative; boundary=047d7b1117c1ae0c0b04f61cff88
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WVaZF-0005pO-7V
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Detailed gitian build guide
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 05:52:02 -0000
--047d7b1117c1ae0c0b04f61cff88
Content-Type: text/plain; charset=UTF-8
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
--047d7b1117c1ae0c0b04f61cff88
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Apr 3, 2014 at 6:47 AM, devrandom <span dir=3D"ltr"><<a href=3D"=
mailto:c1.sf-bitcoin@niftybox.net" target=3D"_blank">c1.sf-bitcoin@niftybox=
.net</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Nice!<br>
<br>
I wonder how much of this could be scripted.<br></blockquote><div><br></div=
><div>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.<br>
<br>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 inst=
alled (in the case of Windows).<br><br></div><div>It may be possible to scr=
ipt *some* parts (most of the quoted bash script is runnable as script) wit=
hout automating the entire process, but I hope that over time we can make G=
itian itself easier to use/setup, so that less steps are needed in the firs=
t place.<br>
</div><div><br>Wladimir<br></div></div><br></div></div>
--047d7b1117c1ae0c0b04f61cff88--
|
