https://bugzilla.redhat.com/show_bug.cgi?id=1324590 --- Comment #19 from paul.j.reger@xxxxxxxxx --- (In reply to Michal Schmidt from comment #18) > (In reply to paul.j.reger from comment #15) > > This is the template for the spec file that we use to generate the > > hfi1-psm.spec file. > > So the resistance to changing the spec file stems from the fact that you are > trying to maintain a common spec file for more than one distribution. That's > not how packaging for distributions is usually done (though it's not > unprecedented either). > > Realize that you are not going to be the only person making changes to the > spec file in Fedora. Any Fedora 'provenpackager' is allowed to make changes > (they should have a good reason to). Release engineers will occasionally > bump the release number of all packages when doing mass rebuilds after > significant toolchain changes. Preventing any divergence is going to be > almost impossible. Yes, we are trying to use one 'template' spec file to support multiple distributions. 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. And since there are two git repositories, the same collection of source on the two git repos may have different release versions. I guess we need to solve these problems now. -- 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