-
Notifications
You must be signed in to change notification settings - Fork 176
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
[FR] - Allow custom tar name #101
Comments
I have no way to evaluate if this is a reasonable feature or not. The %setup docs seem to talk about unpacking source tarballs, but then rpmbuild would try to build them, which is exactly what we wouldn't do with bazel. Can you provide an example of what the goal is, and how you would expect to use it? |
I think this would be a generally useful feature, beyond just the problem identified above (which I confess I don't understand). As my team works with |
I have to say, I don't understand the %setup thing either. I don't use RPM enough to understand the nuances. |
Heh, yes, the proposals in #193 are a more complicated approach to creating the archive name (as well as |
#193 is now ready for review. It will allow you to rename archives any way you want. |
Resolved by #198. |
Problem
When creating an RPM, I'd like to use the
%setup
macro, which I believe assumes you have a tar file with the sameNVR
. As it currently stands thetar
rule will default to using the label name. I'd like to make this configurable (also using --define) with the default going to the label. I'd be happy to open a PR!Goal
Allow users to modify tar name.
The text was updated successfully, but these errors were encountered: