[Git][reproducible-builds/reproducible-website][master] 3 commits: docs(virtual-macchine_drivers): remove bitcoin reference from Gitian

[Mattia Rizzolo (@mattia)]

Mattia Rizzolo pushed to branch master at Reproducible Builds / reproducible-website


Commits:
1385683f by hulkoba at 2024-08-23T15:21:14+00:00
docs(virtual-macchine_drivers): remove bitcoin reference from Gitian

Bitcoin recently moved to Guix, and this project is now archived.

See https://gitian.org/ and https://github.com/devrandom/gitian-builder

- - - - -
4575a1fa by hulkoba at 2024-08-23T15:21:14+00:00
docs(vmd): fix bazel docker link

- - - - -
159a16ed by hulkoba at 2024-08-23T15:21:14+00:00
docs(vmd): keep gitian info and link bitcoin transition plan

where they plan to switch from Gitian to Guix

- - - - -


1 changed file:

- _docs/virtual_machine_drivers.md


Changes:

=====================================
_docs/virtual_machine_drivers.md
=====================================
@@ -17,19 +17,18 @@ builds in mind.
 Gitian
 ------
 
-[Gitian](https://gitian.org/) is the tool [used by
-Bitcoin](https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md).
-It either runs in a Linux container using LXC, or in a virtual machine
-using KVM.
+[Gitian](https://gitian.org/) is a secure source-control oriented
+software distribution method. The Gitian Builder
+[was previously used by Bitcoin Core](https://github.com/bitcoin/bitcoin/issues/21145)
+for deterministic builds for about 10 years.
 
-Gitian takes
-“[descriptors](https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-descriptors/)”
-as input which tell which base GNU/Linux distribution to use, which
-packages to install, which Git remotes to fetch, which other input
-files to use, and a build script to be run with all of that. As explained
-earlier, using a virtual machine helps to get rid of several extra
-variations that can happen from one system to the next.  But this is
-more complicated to setup for users.
+It either runs in a Linux container using LXC, or in a virtual machine using
+KVM. Gitian takes descriptors as input which tell which base GNU/Linux
+distribution to use, which packages to install, which Git remotes to
+fetch, which other input files to use, and a build script to be run
+with all of that. As explained earlier, using a virtual machine helps
+to get rid of several extra variations that can happen from one system
+to the next.  But this is more complicated to setup for users.
 
 rbm
 ---
@@ -58,7 +57,7 @@ To be sure that the base compiler is the same, one could use the fact
 that Docker images can actually be addressed by a hash of their content.
 Another option is to build the Docker image oneself in a reproducible
 manner, something that can be done using
-[Bazel](https://bazel.io/docs/be/docker.html).
+[Bazel](https://bazel.build/install/docker-container).
 
 Vagrant
 -------



View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/eb9e7c0e764c7ac5ccae2adca266e9017a9bae8f...159a16ed8da6dc45f0503a53d9d2833385dc29fe

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/eb9e7c0e764c7ac5ccae2adca266e9017a9bae8f...159a16ed8da6dc45f0503a53d9d2833385dc29fe
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20240823/5c6b45a3/attachment.htm>