Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.54 as permitted sender)
	client-ip=209.85.215.54; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f54.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com>
References: <CAEz79PrAg=yydd3UOk51wGQUWey-KZHUH1Npzwb=qL+6zTj+pQ@mail.gmail.com>
	<53581D1D.1000709@gmail.com>
	<CAEz79Poy0XEVyC=nOdhYNVOASvfB-2zHJcjU2hvjA7iDWGDDyw@mail.gmail.com>
Date: Wed, 23 Apr 2014 15:28:02 -0700
Message-ID: <CAAS2fgSQ6rh1XKao6pv8BmpeRbtqWfUOVF+C1Fi3LEzY1YcPiA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: "Warren Togami Jr." <wtogami@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Precedence: list

On Wed, Apr 23, 2014 at 1:39 PM, Warren Togami Jr. <wtogami@gmail.com> wrot=
e:
> If you are
> a rare user who needs Bitcoin-Qt on an incompatible system you can at lea=
st
> build it from source.

Tails users usually can't really build it from source=E2=80=94 talks is a l=
ive
boot mostly stateless linux distribution for privacy applications.
It's really good in general.

I agree that we shouldn't be statically linking QT on linux generally
(due to things like theming), though maybe we could just have the
build process dump out a seperate extra static QT binary just for
these other cases? I feel like the work maintaining it would be less
than what we've had in answering questions/complaints about it.