https://bugzilla.redhat.com/show_bug.cgi?id=1324590 --- Comment #25 from Michal Schmidt <mschmidt@xxxxxxxxxx> --- (In reply to paul.j.reger from comment #19) > Yes, we are trying to use one 'template' spec file to support multiple > distributions. It's fine if you want to use that for your (upstream) development and testing. But I'm afraid you'll have to drop the requirement that distributions use the exact generated spec file. Some divergence is to be expected. You could treat the spec file in Fedora as a fork of the upstream spec file and cherry-pick changes from one to the other as they are made in either repo. > But, that is only one of the things that we want. Another > is we want our own private git repo here at Intel, and from our own private > git repo, we want to sync a 'mirror' of the repo on github. > A problem with this scheme (that we wish would just go away) is we are > deriving the 'release-version' of our code using git, and literally, that > translates to the number of commits past the version. RPM has the separate concepts of Version and Release in order to have the upstream in control of Version and the packager (who's not necessarily involved in the upstream development) in control of Release. Again, you can keep using this scheme for the packages you make for your upstream development and testing needs. However, for the spec file that's to be shipped in Fedora you have to let go of absolute control of the Release field. (In reply to Ira Weiny from comment #20) > How are changes by other packagers tracked? Every Fedora package has a git repository where the spec file and possible Fedora-specific patches are kept: http://pkgs.fedoraproject.org/cgit/rpms/ (In reply to paul.j.reger from comment #24) > I have since re-worked this change so that the .tar.gz file is referenced > from an URL on git hub. Thank you. I will do another review iteration. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx