On Tue, Jan 12, 2016 at 5:02 PM, Ruediger Meier
On Tuesday 12 January 2016, Neal Gompa wrote:
On Tue, Jan 12, 2016 at 4:43 PM, Jan Engelhardt
wrote: On Tuesday 2016-01-12 19:27, Neal Gompa wrote:
No. Rawhide is rolling and the version may change over time.
So is openSUSE:Factory/Tumbleweed, yet this one has a version.
Keep in mind that %{fedora_version} is an OBS-specific macro, whereas %{fedora} is the one provided by the distribution. Both are supported by OBS, but the latter is native to the distribution.
So %fedora is safe to be used instead of %fedora_version? It will also be expanded and removed in the specfile of the src.rpm?
Not in rawhide (since the macros are processed at rpmbuild, but not obs-build), but in released versions, it should.
As for Factory/Tumbleweed, it's easier for them to do that because the distro is engineered within the build.o.o instance itself. Rawhide is not, which means it must be externally tracked.
I guess it wouldn't be too much work if the one who imports next released Fedora XX also increases Rawhide's version macro.
Otherwise it could be also ok to set fedora_version=99 forever for Rawhide.
If someone on the build-o-o team would prefer to track it more closely, then they could watch the Fedora schedules for the branching point and bump the %{fedora} and %{fedora_version} macros if they want to include them in the rawhide definitions, along with adding the branched release target.
cu, Rudi
-- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org