We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When we specify contents using bazel references, the resulting rpm has the symlink instead of the actual file.
contents
contents: - src: "{{ index .Dependencies `@//cmd/rpm:binary}}" dst: "/bin/binary"
Starting with nfpm v2.13.0, symlinks are preserved instead of being evaluated. See PR goreleaser/nfpm#453
When nfpm_package is used, the bazel-out paths are symlinks back to the execroot. Since those links aren't evaluated, nfpm copies the symlinks as is.
nfpm_package
I think the change is to evaluate the symlink here so that the bazel file output is directly referenced by nfpm.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When we specify
contents
using bazel references, the resulting rpm has the symlink instead of the actual file.Starting with nfpm v2.13.0, symlinks are preserved instead of being evaluated. See PR goreleaser/nfpm#453
When
nfpm_package
is used, the bazel-out paths are symlinks back to the execroot. Since those links aren't evaluated, nfpm copies the symlinks as is.I think the change is to evaluate the symlink here so that the bazel file output is directly referenced by nfpm.
The text was updated successfully, but these errors were encountered: