On Mon, Nov 13, 2006 at 01:55:29PM +0100, Michael Schroeder wrote:
On Fri, Nov 10, 2006 at 11:34:02AM +0100, Dominique Leuenberger wrote:
Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1)
Yes, but n is at least as big as the number in the spec file.
And yes, there should be a way to tell the build service to not mess with the release number.
When pondering future implementation possibilities, it would be nice
to have the build service modifiy the release number by appending its
build revision to the release, not just overwriting it; e.g. X.n where
n is added by the buildservice. For all the packages I have in the
buildservice (currently, anyway), the release number as submitted is
the subversion repository version number; I'd like to keep that intact
in some way so that I can do a reverse mapping from a package back to
the specific version in subversion.
(I'd prefer to avoid adding my repo version to the Version number for
the package, if possible.)
--
Steve Beattie
SUSE Labs, Novell Inc.