Unverified Commit 36a1538a authored by boklm's avatar boklm
Browse files

Don't show detailed build logs on stdout

To provide a more "high level" view of progress, don't output build logs
of each componets on stdout, but write them in files in the logs/ directory.

This idea was suggested by mcs and Kathy in this comment:
https://trac.torproject.org/projects/tor/ticket/17379#comment:12
parent 0e186240
......@@ -7,3 +7,4 @@ alpha_nightly
nightly
hardened
rbm.local.conf
logs
rbm @ b0382ccc
Subproject commit 3fdeb23bc4ab4dc65e69ff0fac49db603c4efb08
Subproject commit b0382ccc58b9286e066bf5980f80cf041e287067
......@@ -2,6 +2,7 @@
debug: '[% GET ! ENV.RBM_NO_DEBUG %]'
compress_tar: gz
output_dir: "out/[% project %]"
build_log: 'logs/[% project %]-[% c("var/osname") %].log'
pkg_type: build
......
......@@ -22,6 +22,11 @@
### use the same docker image names.
#docker_image_prefix: tor-browser_XXXXX
### The build_log option defines in which file the build logs of each
### component are stored. If you set it to '-' the logs are output on
### stdout and stderr.
#build_log: '-'
var:
local_conf: 1
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment