From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1Wd5eE-0000hu-Ep
	for bitcoin-development@lists.sourceforge.net;
	Wed, 23 Apr 2014 22:28:10 +0000
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; 
Received: from mail-la0-f54.google.com ([209.85.215.54])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Wd5eD-0004Lk-Lh
	for bitcoin-development@lists.sourceforge.net;
	Wed, 23 Apr 2014 22:28:10 +0000
Received: by mail-la0-f54.google.com with SMTP id e16so1059588lan.27
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 23 Apr 2014 15:28:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.94.229 with SMTP id df5mr3622887lbb.36.1398292082830;
	Wed, 23 Apr 2014 15:28:02 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Wed, 23 Apr 2014 15:28:02 -0700 (PDT)
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
X-Spam-Score: -1.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
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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: 1Wd5eD-0004Lk-Lh
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
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, 23 Apr 2014 22:28:10 -0000

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.