On 10/03/11 - 04:44:16PM, James Laska wrote:
A pre-release is any release where %{release} starts with 0. When
building RPMs of pre-releases, a datestamp and githash are included in
the RPM %{release} string. This allows to easily determine when and
what is included in the built packages.
---
oz.spec.in | 2 +-
setup.py | 18 +++++++++++++++---
2 files changed, 16 insertions(+), 4 deletions(-)
I feel like we can be a bit more pythonic about this. I've taken your patch
and modified it a bit; the result is attached. Please take a look and tell
me what you think.
There is one bit about this I still don't like. Right now when I go to do a
release, I only have to the VERSION field in setup.py, and things will work
properly. By moving to this new scheme, I have to change VERSION in setup.py
and Release in oz.spec.in. I think I might rather move the Release field into
setup.py, and then at least I would only have a single file to change (even if
I do have to change 2 fields).
--
Chris Lalancette