Commit 361cf8c
tools: don't gitignore base64 config.h
The file is checked into git. Ignoring it causes a very non-obvious way
of breaking tarball builds:
1. Download and unpack tarball
2. Check the sources into git with `git init; git add .; git commit -a`
3. Clean the source tree with `git clean -dfx`
4. Run `./configure && make`
5. Observe build failure because config.h is missing
Fixes: #47638
PR-URL: #48174
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>1 parent 0cfdb3a commit 361cf8c
1 file changed
Lines changed: 5 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -57,7 +57,11 @@ mv "$WORKSPACE/base64" "$DEPS_DIR/base64/" | |||
| 57 | 57 | ||
| 58 | 58 | # Build configuration is handled by `deps/base64/base64.gyp`, but since `config.h` has to be present for the build | |
| 59 | 59 | # to work, we create it and leave it empty. | |
| 60 | - echo "// Intentionally empty" >> "$DEPS_DIR/base64/base64/lib/config.h" | ||
| 60 | + echo "// Intentionally empty" > "$DEPS_DIR/base64/base64/lib/config.h" | ||
| 61 | + | ||
| 62 | + # Clear out .gitignore, otherwise config.h is ignored. That's dangerous when | ||
| 63 | + # people check in our tarballs into source control and run `git clean`. | ||
| 64 | + echo "# Intentionally empty" > "$DEPS_DIR/base64/base64/.gitignore" | ||
| 61 | 65 | ||
| 62 | 66 | echo "All done!" | |
| 63 | 67 | echo "" | |
0 commit comments