You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
All C/C++ SRPM generated with the commit 30f5327 contain only the SPEC file. However, the SRPM for Python packages contain the source code and can rebuild the binary package.
All SRPM should contain the SPEC file along with the sources (archive + patches), so that they can be rebuilt with rpmbuild.
My recommendation would be to use git archive to generate an archive from a given commit and use it to create the SRPM. Once the SRPM is properly created, building the RPM out of it is a trivial task (except, maybe, in case of cross-compilation). The drawback is that RPM cannot be built from a "dirty" commit. However, I would consider this as an advantage which encourages good practice.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
All C/C++ SRPM generated with the commit 30f5327 contain only the SPEC file. However, the SRPM for Python packages contain the source code and can rebuild the binary package.
All SRPM should contain the SPEC file along with the sources (archive + patches), so that they can be rebuilt with
rpmbuild
.My recommendation would be to use
git archive
to generate an archive from a given commit and use it to create the SRPM. Once the SRPM is properly created, building the RPM out of it is a trivial task (except, maybe, in case of cross-compilation). The drawback is that RPM cannot be built from a "dirty" commit. However, I would consider this as an advantage which encourages good practice.The text was updated successfully, but these errors were encountered: