Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tor-reproducer
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
briar
tor-reproducer
Commits
752b1114
Verified
Commit
752b1114
authored
1 year ago
by
Sebastian
Browse files
Options
Downloads
Patches
Plain Diff
Explain upstream build system and hacking it
parent
b585086a
No related branches found
Branches containing commit
No related tags found
2 merge requests
!34
Use tor-0.4.7.14 in upstream buildsystem
,
!33
Add tor-0.4.7.14
Pipeline
#15162
passed with warnings
1 year ago
Stage: build
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+19
-0
19 additions, 0 deletions
README.md
with
19 additions
and
0 deletions
README.md
+
19
−
0
View file @
752b1114
...
...
@@ -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.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment