| commit | 53f4950eea0287272aac3c3f7b2064742462dbc6 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Mon Jul 25 18:40:02 2016 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Mon Dec 19 15:17:26 2016 -0800 |
| tree | 77f60aaf20b58bc0555861c6fedeac4504cc7ac8 | |
| parent | f3218f61b676ba192714381b64ddfa3243f615dc [diff] |
Prevent glob from accessing hidden files
Hidden files are often source control related (".git", ".repo", etc) or
editor related (vim's .*.swp), so are not guaranteed to exist, and may
be temporary. The build system shouldn't be using these files by
default.
If the glob pattern explicitly uses "." at the beginning of a path
component, allow returning hidden files for that component. Because of
this behavior, non-wildcard globs remain unchanged.
The one behavior that cannot be handled anymore is including hidden
files in recursive globs.
Change-Id: I583c506e9a18ed2ff7ca011a791165d9582de90f
- pathtools/glob.go[diff]
- pathtools/glob_test.go[diff]
- pathtools/testdata/.test/.ing[Added - diff]
- pathtools/testdata/.test/a[Added - diff]
- pathtools/testdata/.testing[Added - diff]
5 files changed
tree: 77f60aaf20b58bc0555861c6fedeac4504cc7ac8
- bootstrap/
- bpfmt/
- bpmodify/
- deptools/
- gotestmain/
- gotestrunner/
- loadplugins/
- parser/
- pathtools/
- proptools/
- tests/
- .gitignore
- .travis.fix-fork.sh
- .travis.gofmt.sh
- .travis.install-ninja.sh
- .travis.yml
- blueprint.bash
- Blueprints
- bootstrap.bash
- build.ninja.in
- context.go
- context_test.go
- CONTRIBUTING.md
- doc.go
- fs.go
- glob.go
- LICENSE
- live_tracker.go
- mangle.go
- module_ctx.go
- ninja_defs.go
- ninja_strings.go
- ninja_strings_test.go
- ninja_writer.go
- ninja_writer_test.go
- package_ctx.go
- README.md
- scope.go
- singleton_ctx.go
- splice_modules_test.go
- unpack.go
- unpack_test.go
- visit_test.go
README.md
Blueprint Build System
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja manifest describing the commands that need to be run and their dependencies. Where most build systems use built-in rules or a domain-specific language to describe the logic for converting module descriptions to build rules, Blueprint delegates this to per-project build logic written in Go. For large, heterogenous projects this allows the inherent complexity of the build logic to be maintained in a high-level language, while still allowing simple changes to individual modules by modifying easy to understand Blueprints files.