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
Generate source RPMs #3136
Comments
not sure how much effort is required for this, will have to investigate... |
cc/ @goreleaser/nfpm thoughts? |
I'm not really sure how source RPMs look internally and I always find it hard to find good documentation that is useful for implementers instead of users. Are they structured differently from regular RPMs or do they only differ in their contents (e.g. source code instead of binaries and build scripts instead of install scripts)? I they differ only in content I guess they can be built with However, my personal vision of |
My understanding is that SRPM packages are tar archives with the source archive in a Note that the dependency on the source archive means that this functionality might need to be implemented in GoReleaser, not in nfpm. |
In this case, this should probably be a |
Should this issue be transferred back to goreleaser? |
FWIW you don't need source rpms to package a Go module on Fedora COPR, a spec file is enough. Fedora recommends you generate the spec file with go2rpm. This worked for me. Debian have a similar command |
Is your feature request related to a problem? Please describe.
@dngray in twpayne/chezmoi#1800 requested that a project released with Goreleaser should be available in Copr. Copr builds RPMs for multiple RedHat-like distributions, and takes a source RPM (
.src.rpm
) from a public website as input.Right now, Goreleaser (building on nfpm) builds RPMs but not source RPMs.
Describe the solution you'd like
I would like Goreleaser to build source RPMs as an additional output.
Describe alternatives you've considered
Search
Code of Conduct
Additional context
I would be happy to implement this if you think it's a good idea.
The text was updated successfully, but these errors were encountered: