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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1QrCqi-0004qQ-QM
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Aug 2011 17:45:48 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.83.47 as permitted sender)
client-ip=74.125.83.47; envelope-from=witchspace81@gmail.com;
helo=mail-gw0-f47.google.com;
Received: from mail-gw0-f47.google.com ([74.125.83.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1QrCqi-0003Cf-0p
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Aug 2011 17:45:48 +0000
Received: by gwb11 with SMTP id 11so1065921gwb.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 10 Aug 2011 10:45:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.114.2 with SMTP id m2mr9087526ybc.3.1312998342258; Wed, 10
Aug 2011 10:45:42 -0700 (PDT)
Received: by 10.150.52.5 with HTTP; Wed, 10 Aug 2011 10:45:41 -0700 (PDT)
In-Reply-To: <CABsx9T0Yvssr04AeT3B8+Gj43hV=P0Uw6M0f+NBNygnAyruQ4A@mail.gmail.com>
References: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com>
<1312971289.3253.6.camel@BMThinkPad.lan.bluematt.me>
<20110810104316.GA30749@ulyssis.org>
<CAJNQ0ssWeU2vgR8XmCyGiZ3UHPv=zjLZEKVM=gqP0ozSC7Wmiw@mail.gmail.com>
<CAJNQ0stkZ=iBCJA7E5+LZToe2MjEJnhqWoiUtLcqTGPygSikiA@mail.gmail.com>
<CABsx9T0Yvssr04AeT3B8+Gj43hV=P0Uw6M0f+NBNygnAyruQ4A@mail.gmail.com>
Date: Wed, 10 Aug 2011 17:45:42 +0000
Message-ID: <CAJNQ0stfYFN2YCGq-be5D-XW+81ZkVVM_jHHonSy2OHsNyN1Cw@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd48bc6c7f0a804aa2a3f16
X-Spam-Score: -0.5 (/)
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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QrCqi-0003Cf-0p
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Change to multiple executables?
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: Wed, 10 Aug 2011 17:45:48 -0000
--000e0cd48bc6c7f0a804aa2a3f16
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Aug 10, 2011 at 4:49 PM, Gavin Andresen <gavinandresen@gmail.com>wrote:
> RE: splitting off the "send commands to a running bitcoin" :
>
> I'm mildly against it. It would be less confusing for newbies, at the
> cost of forcing everybody who has already written backup scripts or
> other interact-with-running-bitcoin tools to tweak their code. The
> coding will be easy, but do you really want to spend the time to
> answer all the "I installed Bitcoin X.Y and now my backup script
> doesn't work" questions and modify the wiki pages and ...
>
As the project is still in "experimental" phase I suppose people can expect
changes like this? And the change is pretty much trivial, and it makes sense
for a future direction (UI<->Wallet in separate processes for security
concerns).
To be honest I feel a bit like every change that I (and I've also heard this
from others) propose is shot down, no matter how well formulated. This is
actively discouraging developers from joining this project.
Of course it makes sense to be a careful, but the project is not on life
support is it? Satoshi did a great job making the program, but his work was
not perfect, and it makes sense to look ahead a bit.
I think it would be better to switch to two branches, like most other open
source projects I've worked with:
0.3.x -> small, compatible changes, bugfixes, like now
0.4.x -> trunk, more impactful changes, refactorings, eventual major release
Both will obviously be fully compatible on the P2P-level.
> I'd rather that time be spent working on any remaining build issues so
> we can switch to bitcoin-qt. I don't care if it is autotools or qmake
> or QT creator, I just care that it works on Windows and Linux under
> gitian and has clear instructions so I can build it on my Mac.
>
I could do the Gitian stuff but not the Mac instructions, as I don't have a
Mac...
JS
--000e0cd48bc6c7f0a804aa2a3f16
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_quote">On Wed, Aug 10, 2011 at 4:49 PM, Gavin Andre=
sen <span dir=3D"ltr"><<a href=3D"mailto:gavinandresen@gmail.com">gavina=
ndresen@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
RE: splitting off the "send commands to a running bitcoin" :<br>
<br>
I'm mildly against it. It would be less confusing for newbies, at the<b=
r>
cost of forcing everybody who has already written backup scripts or<br>
other interact-with-running-bitcoin tools to tweak their code. The<br>
coding will be easy, but do you really want to spend the time to<br>
answer all the "I installed Bitcoin X.Y and now my backup script<br>
doesn't work" questions and modify the wiki pages and ...<br></blo=
ckquote><div><br>As the project is still in "experimental" phase =
I suppose people can expect changes like this? And the change is pretty muc=
h trivial, and it makes sense for a future direction (UI<->Wallet in =
separate processes for security concerns).<br>
<br>To be honest I feel a bit like every change that I (and I've also h=
eard this from others) propose is shot down, no matter how well formulated.=
=A0 This is actively discouraging developers from joining this project.<br>
<br>Of course it makes sense to be a careful, but the project is not on lif=
e support is it? Satoshi did a great job making the program, but his work w=
as not perfect, and it makes sense to look ahead a bit.<br><br>I think it w=
ould be better to switch to two branches, like most other open source proje=
cts I've worked with:<br>
<br>0.3.x -> small, compatible changes, bugfixes, like now<br>0.4.x ->=
; trunk, more impactful changes, refactorings, eventual major release<br><b=
r>Both will obviously be fully compatible on the P2P-level.<br><br></div>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I'd rather that time be spent working on any remaining build issues so<=
br>
we can switch to bitcoin-qt. =A0I don't care if it is autotools or qmak=
e<br>
or QT creator, I just care that it works on Windows and Linux under<br>
gitian and has clear instructions so I can build it on my Mac.<br></blockqu=
ote><div><br>I could do the Gitian stuff but not the Mac instructions, as I=
don't have a Mac... <br><br>JS<br></div></div>
--000e0cd48bc6c7f0a804aa2a3f16--
|
