public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kristov Atlas <author@anonymousbitcoinbook.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Date: Wed, 23 Apr 2014 21:56:23 -0400	[thread overview]
Message-ID: <53586F47.1000606@anonymousbitcoinbook.com> (raw)
In-Reply-To: <CAAS2fgSQ6rh1XKao6pv8BmpeRbtqWfUOVF+C1Fi3LEzY1YcPiA@mail.gmail.com>


On 04/23/2014 06:28 PM, Gregory Maxwell wrote:
> 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.
>
> 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.
>
> ------------------------------------------------------------------------------
Dumping out a separate, extra static QT binary is a great idea.



  reply	other threads:[~2014-04-24  2:24 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 [this message]
2014-04-24  8:02       ` Wladimir
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=53586F47.1000606@anonymousbitcoinbook.com \
    --to=author@anonymousbitcoinbook.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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