diff options
| author | bors <bors@rust-lang.org> | 2018-08-30 17:29:13 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-08-30 17:29:13 +0000 |
| commit | f8d34596ff74da91e0877212a9979cb9ca13eb7e (patch) | |
| tree | 46b99e38d06320c792945c2f5489e468d30720d2 /src/libsyntax/parse | |
| parent | 685fb543174f8f2cadc38ec0b2c6df635eb1c087 (diff) | |
| parent | 38e2d00152358ed6021d1853a792cf3b9c9ae5c4 (diff) | |
| download | rust-f8d34596ff74da91e0877212a9979cb9ca13eb7e.tar.gz rust-f8d34596ff74da91e0877212a9979cb9ca13eb7e.zip | |
Auto merge of #53803 - pietroalbini:fix-manifest-2, r=alexcrichton
Fix manifests for broken tools: take 2 This is a follow up of #53715, to avoid stripping unavailable components from the extensions list. This time I also figured out how to test the changes, so the produced manifest is correct. Along with the fix I added a README with instructions on how to test the tool, and a new `BUILD_MANIFEST_DISABLE_SIGNING` env var to avoid dealing with gpg while testing the tool. I chose an env var instead of a flag because it's more difficult to have it slip in by accident on CI, and there is also another protection that panics if that env var is set on CI, just to be sure we don't release unsigned artifacts. r? @alexcrichton cc https://github.com/rust-lang-nursery/rustup.rs/issues/1486
Diffstat (limited to 'src/libsyntax/parse')
0 files changed, 0 insertions, 0 deletions