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
It would be reasonable straightforward to turn that into a .j2 file which would allow "rpmbuilt -ta" from the ansible tarball, if desired, and potentially support a "--redhat" option to go along with the "--debian" packaging option.
The text was updated successfully, but these errors were encountered:
May I suggest using https://packit.dev instead of (or additionally to) templating? That project exists specifically to allow having upstream spec files and they may even provide continuous testing on their platform via a GitHub App at https://github.com/marketplace/packit-as-a-service.
I strongly dislike this idea. The point is to get the tarball, itself, to contain the matching .spec file, and to be able to run the command "rpmbuild -ta ansible-5.0.1.tar.gz" to generate a locally assembled RPM.
I've some functional files for RPM building over at https://github.com/nkadel/ansiblerepo/blob/master/ansible-5.x-srpm/ansible.spec
It would be reasonable straightforward to turn that into a .j2 file which would allow "rpmbuilt -ta" from the ansible tarball, if desired, and potentially support a "--redhat" option to go along with the "--debian" packaging option.
The text was updated successfully, but these errors were encountered: