How should the spec-files stored in source-git look like?
One idea I think makes sense is that spec-files in source-git should have no Patch* lines in them, as there are no patch-files stored in source-git. These lines should be added by the tool transforming the source-git content to dist-git. One implementation of this can be already found in Packit (see this doc).
Patch*
We store the spec as a spec.template and use make dist-git to call a script which sets it up as the spec for a release. I don't think that a lack of patch line is the goal, perhaps an empty patch file which gets filled in? It also makes it easier for users to test out a patch as they can just cat their patch to that file.
I'm personally in favour of having spec files in the source-git repo without Patch lines - since those live as commits in the repo. We can easily have a tooling to populate the spec with patch definitions and generate patch files.
I wonder if spec templating would be an option which more projects would find useful (I'd like to know why - what are the exact benefits :)
Log in to comment on this ticket.