https://bugzilla.novell.com/show_bug.cgi?id=271712
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=271712#c30
--- Comment #30 from Jeff Mahoney 2008-02-23 15:57:19 MST ---
We're in -rc land again, so I'd like to revisit this and maybe even fix it
permanently.
Rudi, does that work for mbuild too? I have a get_release_number.sh.in that
gets processed as part of tar-up.sh, but it looks like it gets ignored. For the
current head kernel, the processed version looks like:
#! /bin/sh
case $3 in
kernel-dummy)
echo "0.rc2.git6.$2" ;;
*)
echo "pkg: kernel-dummy" ;;
esac
.. but I end up with kernel-default-2.6.25-4.$arch.rpm instead of
kernel-default-2.6.25-0.rc2.git6.4.$arch.rpm as I expected.
Michael, is it possible to use that trick in a spec file?
Checking in an updated project.conf requires an extra step outside of the
normal tar-up.sh process. I was hoping I could do something like this in the
spec file:
Version: @RPMVERSION@
%if 0%{?opensuse_bs}
Release: @OBSRELEASE@
%else
Release: 0
Where, processed for 2.6.25-rc2-git6, it would look like:
Version: 2.6.25
%if 0%{?opensuse_bs}
Release: 0.rc2.git6..
%else
Release: 0
%endif
When the builds are no longer based on release candidates, it would just
evaluate to ., automatically generating a release major higher
than 0.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.