-
Notifications
You must be signed in to change notification settings - Fork 84
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
Regression: short form repository labels don't work anymore #41
Comments
I don’t understand where the symlink was before. IIRC I didn’t remove any symlinks (perhaps implicitly?). Since We only control the target repository if it was fetched via |
@Profpatsch The symlink wasn't needed because of the |
Yeah, that’s what I suspected. But then I don’t see how it defaulted to the target anyway. |
Before #29, we'd write ```python nixpkgs_package(name = "hello", repository = "@nixpkgs") ``` and this would just work. Now we write ```python nixpkgs_package(name = "hello", repositories = { "nixpkgs": "@nixpkgs//:default.nix" }) ``` which is quite a bit more verbose. With this fix, writing the repository label as `"@nixpkgs"` works again. Fixes #41.
Before #29, we'd write ```python nixpkgs_package(name = "hello", repository = "@nixpkgs") ``` and this would just work. Now we write ```python nixpkgs_package(name = "hello", repositories = { "nixpkgs": "@nixpkgs//:default.nix" }) ``` which is quite a bit more verbose. With this fix, writing the repository label as `"@nixpkgs"` works again. Fixes #41.
It used to be possible to write this:
This is a lot shorter than
repositories = {"nixpkgs": "@nixpkgs//:default.nix"}
. The reason this worked before is that we had a symlink that had the same name as the repository, pointing todefault.nix
, since@foo
is actually syntactic sugar for@foo//:foo
in Bazel.It would be nice to have this shorthand available again. Incidentally, I think we should not deprecate
repository
, even thoughrepositories
now exists.The text was updated successfully, but these errors were encountered: