-
Notifications
You must be signed in to change notification settings - Fork 295
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 LICENSE file to RPMs #267
Conversation
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.
Thanks @matthewtorr-msft! I'll let CI run on it first and then check it out to take a closer look.
We should also do this for the other types of installers so that we are consistent throughout the project.
@matthewtorr-msft After checking out the RPM docs, I agree that your change should be working. However, when I build locally with
Could I have you take a look at it? Also, could you share your error message if the build is not working for you? Thanks! |
If I run
If I run from the root of the repo, here is the whole output which has several kinds of errors:
|
I think the macros probably only work if you use the default build directory (regular
So you probably need something like
Translates to "don't create the usual directory, create something called src and add app to it" Not sure why the copy doesn't fail properly, but then again - C and error checking, hmm |
I think I understand now how the cri-docker.socket file is packaged in, I'll push some further changes based on that and you can see if it works |
The other files are using some hack with the "usual paths", instead of the regular SOURCE macros
Not sure why they don't use the source files (from It made sense when we just used a binary tarball (without sources), and not building the go code. |
@matthewtorr-msft I usually run |
I just realized I still had the build fix in place also. Updating the golang version for the updated packages fixes the issue: #268 |
Great news, thanks. To be clear, is that with the original patch or the updated version? I'll undo the updates if not needed. |
Without the updated golang version, you will get an error (currently on master) from one of the dependencies for building packages that it needs go 1.19+. None of the LICENSE fill changes have worked for me but bumping that image version will let you test it. |
I've got this working locally and pushed the changes. Thanks for the go version tip, I needed that to make it work locally. However, I also needed to change the VERSION line in packaging/common.mk from "?=" to ":="--some of my errors above were due to VERSION not being defined. I haven't committed this as it seems to be working for you. Unsure why we're seeing different behaviour! |
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 and built for me locally.
Thanks for the contribution and being patient with getting it merged in!
No worries, thank you for being responsive and helping me get it to work! |
The hardcoded paths probably doesn't matter as much, since this is only run from the Docker container anyway. |
Fixes #266
This adds the LICENSE files to RPMs.
Unfortunately I haven't been able to get the RPM builds working locally so I've not been able to test it, though it should "just work". (That assumes all target distros have rpm 4.11 or above; if not, %doc would be a suitable alternative.)