| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
target pattern.
Apart from the tests, I also tested this manually running "bazel query //..." in a tree with convenience symlinks.
--
MOS_MIGRATED_REVID=108325454
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN" will *not* be traversed for transitive target patterns. The motivation here is to allow directories that intentionally contain wonky symlinks (e.g. foo/bar -> foo) to opt out of being consumed by Blaze. For example, given
<workspace>/foo
bar
bad -> .
DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
the 'bad' symlink will *not* be traversed by the pattern '//foo/...'.
--
MOS_MIGRATED_REVID=107738930
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87717872
|
|
|
|
|
|
|
| |
Having an error message in path/to/package and //path/to/package resolve to //path/to/package:package was a bit strange.
--
MOS_MIGRATED_REVID=87171051
|
|
--
MOE_MIGRATED_REVID=85702957
|