Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add .bazelignore to skip deb_packages, examples subdirectories #457

Merged
merged 1 commit into from
Nov 4, 2021

Conversation

nacl
Copy link
Collaborator

@nacl nacl commented Nov 4, 2021

As of #443, all of the rules_pkg files are now in a WORKSPACE relative to the
root of the repository. These are now shared with the deb_packages/ and
examples/ subdirectories, which contain their own WORKSPACE files. This
confuses Bazel and prevents us from testing //....

This changes allows us to build/test //... by adding those directories to a
.bazelignore file at the root of the repository.

Most people working on rules_pkg aren't going to be touching these, and if they
are, they need to be in those WORKSPACEs anyway, so there should be no harm in
this.

As of bazelbuild#443, all of the rules_pkg files are now in a WORKSPACE relative to the
root of the repository.  These are now shared with the `deb_packages/` and
`examples/` subdirectories, which contain their own WORKSPACE files.  This
confuses Bazel and prevents us from testing `//...`.

This changes allows us to build/test `//...` by adding those directories to a
.bazelignore file at the root of the repository.

Most people working on rules_pkg aren't going to be touching these, and if they
are, they need to be in those WORKSPACEs anyway, so there should be no harm in
this.
@nacl nacl requested a review from aiuto November 4, 2021 19:06
@aiuto aiuto merged commit a922611 into bazelbuild:main Nov 4, 2021
@nacl nacl deleted the topic/bazelignore branch November 9, 2021 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants