https://bugzilla.novell.com/show_bug.cgi?id=271712#c26
Andreas Gruenbacher changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |ro@novell.com
--- Comment #26 from Andreas Gruenbacher 2007-10-31 05:35:39 MST ---
Comment 24: I agree about SLE10. We can continue playing tricks with the
version. We could also try modifying the release number, but that could confuse
Autobuild, because it may not know how to get from one arbitrary release number
like 0.rcX.1 to the next. But these things are just ugly hacks, and if we could
somehow define that 1.2.3~rc1 comes before 1.2.3, that would be much more
obvious to users.
We would nee to hack this into at least rpm, smart, zypper, libzypp, and
perhaps in the SuSE any YUM metadata generators as well. I think the critical
question is whether this approach will get support within the RPM maintainers.
Comment 25: break in that context means tools which will get the package order
wrong. So this more or less should belimited to tools for installing packages.
Hacking the release number is a pretty crappy approach, but I expect most tools
to implement rpm version comparisons correctly, so the only potential problem
I'm aware of right now is with build environments (Autobuild, build service).
how about
Release: rc1.0
That would work; even only incrementing the trailing numeric part without
requiring a specific separator would do. We have the release number
synchronization hack via kernel-dummy though; I don't think we can override the
release number that kernel-dummy uses at the moment. Rudi, any ideas for that
perhaps?
--
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.