Many people use development boards (Raspberry Pi 2, Banana Pi,
Odroid boards, etc) to run full nodes in CLI mode.
The only option they had until now is to compile their own from source.
Even though many tutorials are available, it is still not trivial for
non tech-savvy users.
Providing an officially built armhf binary would provide non tech-savvy
users an easy ramp-on to Bitcoin Classic.
*** GUI has been disabled for this build — according to Qt docs it
needs to be compiled on with device-specific headers. Most armhf users
use it in CLI mode only anyway.
Tested binaries on Raspberry Pi2, Odroid C1 and Odroid XU4.
These are changes I needed to get gitian building to work with Debian
8.2, which is the version we tell to use.
- Set up NAT, so that container can access network beyond host
- Remove explicit cgroup setup - these are mounted automatically now
- gitian: Need `ca-certificates` and `python` for LXC builds
Github-Pull: #7060
Rebased-From: 99fda26de03b468a0e60
done automatically.
At some point along the line, fully offline builds were no longer happening
when strictly following the release-process.md instructions.
We should ensure that users who might want to torify or build offline need
to take extra steps to remain offline.
Also, corrections to build process: including gverify examples for new builders.
I added a link to my guide about using docker containers + LXC (I am planning to maintain this at work
for future bitcoin versions), then I mentioned other virtualization options (KVM, LXC).
This commit includes a fix issue for documentation issue #4269 that consists in telling users to
checkout correct bitcoin version before using the gitian descriptors (otherwise all hell can break loose).
Also, I replaced URL for Debian 7.4 ISO with a correct one and added link to official Debian ISO sources.
The patch to make it possible to configure the LXC IPs has been merged
upstream. This means that it is no longer needed to patch gitian.
Remove that workaround.