Bugzilla – Bug 135826
build.rpm build script does not honor get_version_number.sh
Last modified: 2006-02-16 00:06:09 UTC
The build script does not replace the Version tag with the output of get_version_number.sh in the version that is part of build.rpm on 10.0. This functionality is critical for kernel module (aka driver) packages, which must have the current kernel's version in their version tag. Alternatively to get_version_number.sh, build could be changed to allow rpm macros in the Version field, so that we could use something like: Version: %(rpm -q --qf '%{VERSION}_%{RELEASE}' kernel-source) in spec files. IMHO this would be the much more elegant solution anyway, as vanilla RPM would support it just the same.
It never did, as it does no "prepare_spec". The %() proposal might be elegant, but I don't see how I can implement it as I cannot call rpm from the autobuild scheduler. (It also doesn't call get_version_number.sh...) Hmm, and automatic release number increments on checkin also won't work.
Indeed, we cannot call get_version_number.sh outside of the build environments, either. But we do have some packages where the version is only determined during build, with either mechanism. If Autobuild relies on the package version otherwise, then that's actually broken for such packages. Is there any chance this could be fixed, maybe by using a short-time workaround like writing a magical "version from the last build" into a special file, or whatever?
I guess this is fixed by the new KMP scheme?
It was fixed by allowing macros in the Version tag, which we (you) added in the meantime, thanks.