Skip to content
Snippets Groups Projects
Commit f085e882 authored by akwizgran's avatar akwizgran
Browse files

Merge branch 'explain-upstream-hacking' into 'tor-0.4.7.14'

Use tor-0.4.7.14 in upstream buildsystem

See merge request !34
parents b585086a 752b1114
No related branches found
No related tags found
2 merge requests!34Use tor-0.4.7.14 in upstream buildsystem,!33Add tor-0.4.7.14
Pipeline #15172 passed with warnings
......@@ -80,3 +80,22 @@ reproduce those.
To build a specific version of Tor, run
docker run briar/tor-reproducer:latest ./build_tor.py [version]
### Upstream build system
This repository uses the upstream Tor build system for building macOS
binaries. The `tor-versions.json` file defines the configuration for that
system via the `upstream` stanza.
We maintain our own
[fork](https://code.briarproject.org/briar/tor-browser-build) of the
[tor-browser-build](https://gitlab.torproject.org/tpo/applications/tor-browser-build)
repository so that we're able to define which Tor browser version and
exact upstream commit/tag we're building our Tor binaries from and
additionally have the ability to apply patches.
This makes it for example possible to build Tor binaries with a higher
version number than yet released in a Tor browser release.
We maintain a branch that's based on one of the upstream branches such
as `maint-12.0` but appends a tor version (i.e. `maint-12.0-tor-0.4.7.14`).
Then we create an annotated tag such as `tor-0.4.7.14` from that branch
and use that tag name in the `tor-versions.json` configuration file.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment