From: Wladimir <laanwj@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Date: Thu, 24 Apr 2014 10:02:52 +0200 [thread overview]
Message-ID: <CA+s+GJDY6c2-fjbL=JcrF3umM4ji8Y5j5ppxX_mAzZdTh1_QRw@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSQ6rh1XKao6pv8BmpeRbtqWfUOVF+C1Fi3LEzY1YcPiA@mail.gmail.com>
On Thu, Apr 24, 2014 at 12:28 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Wed, Apr 23, 2014 at 1:39 PM, Warren Togami Jr. <wtogami@gmail.com> wrote:
>> If you are
>> a rare user who needs Bitcoin-Qt on an incompatible system you can at least
>> build it from source.
>
> Tails users usually can't really build it from source— talks is a live
> boot mostly stateless linux distribution for privacy applications.
> It's really good in general.
Aside: But is Bitcoin Core a well-suited application for those uses? I
cannot imagine someone running a full node on a stateless system.
Anyhow: As this is only one symbol, we can probably get rid of it (as
we didn't use it in 0.8.6?), or put it behind some #ifdef
COMPATIBILITY_BUILD...
Another option: Instead of statically building it'd be easy enough to
build against the 4.6 Qt headers instead without even swapping the
library. Qt is, after all, forward-compatible - between the 4.x
versions. This will lose some GUI features but if compatibility is
more important here that's a choice that can be made.
Wladimir
next prev parent reply other threads:[~2014-04-24 8:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:30 [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 Warren Togami Jr.
2014-04-22 14:05 ` Wladimir
2014-04-23 20:05 ` Kristov Atlas
2014-04-23 20:28 ` Wladimir
2014-04-23 20:39 ` Warren Togami Jr.
2014-04-23 20:52 ` Kristov Atlas
2014-04-23 22:28 ` Gregory Maxwell
2014-04-24 1:56 ` Kristov Atlas
2014-04-24 8:02 ` Wladimir [this message]
2014-04-24 8:07 ` Wladimir
2014-04-24 8:15 ` Warren Togami Jr.
2014-04-24 8:25 ` Wladimir
2014-04-24 12:18 ` Wladimir
2014-04-25 20:09 ` Kristov Atlas
2014-04-25 20:47 ` Wladimir
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+GJDY6c2-fjbL=JcrF3umM4ji8Y5j5ppxX_mAzZdTh1_QRw@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
/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