-
Notifications
You must be signed in to change notification settings - Fork 80
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
Implement remaining nix_pkg tags #369
Conversation
🎉 All dependencies have been resolved ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
"$(locations @output-filegroup-test//:include)", | ||
"$(locations {})".format(nix_pkg("rules_nixpkgs_core_testing", "output-filegroup-test", "//:include")), | ||
], | ||
data = ["@output-filegroup-test//:include"], | ||
data = [nix_pkg("rules_nixpkgs_core_testing", "output-filegroup-test", "//:include")], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was a bit confused why the nix_pkg
module extension was being used like this, but now I see nix_pkg
here is a helper macro from defs.bzl
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably something to make clear in the docs. Or, if we end up getting local_use_repo
the problem would go away.
Depends on #364
Part of #183.
Implement the remaining
local_file
andlocal_expr
nix_pkg
tags.Add support for
nixopts
handling. (Apart from location expansion, see below).Ensure each of them is tested in testing/core.
Note on location expansion: The implementation of location expansion for repository rules needs to know the labels as seen at the definition site of the location expansion expression, i.e. the user's MODULE.bazel file. But, the module extension implementation only sees the resolved labels, not their raw string form. The repository rules were able to work around this using a wrapper macro. But, MODULE.bazel files cannot call macros, meaning this workaround is not available.