From: Thomas Zander <thomas@thomaszander•se>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Something people are forgetting about the Gentoo / Luke-jr censorship issue
Date: Fri, 10 Oct 2014 21:02:38 +0200 [thread overview]
Message-ID: <2421098.8lktok9SJz@coldstorage> (raw)
In-Reply-To: <CANEZrP3NDFq8RJMH_OwH=9r3nOvLt4vhToy8qDnLzHb7EsP9iw@mail.gmail.com>
On Friday 10. October 2014 19.26.49 Mike Hearn wrote:
> I'm sure this suggestion will go down like a lead balloon, but Bitcoin Core
> is not the first project that's had issues with Linux distros silently
> modifying their software as they package it.
And so far its been near impossible for those others to make distros not
modify it.
Firefox is actually a good idea, it made debian stop distributing it.
Best solution is to build good relations with the packagers of distros.
ps. Linux distros distributing GPL licensed apps are required by law to offer
the sources of the thing they build and distribute as binary. Which allows you
to check the difference with upstream. Most distros therefore have a process in
place for this. Even for not FLOSS software like bitcoin core.
prev parent reply other threads:[~2014-10-10 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:22 xor
2014-10-10 16:42 ` Jeff Garzik
2014-10-10 17:26 ` Mike Hearn
2014-10-10 18:41 ` Justus Ranvier
2014-10-10 19:02 ` Thomas Zander [this message]
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=2421098.8lktok9SJz@coldstorage \
--to=thomas@thomaszander$(echo .)se \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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