On 09/26/2003 03:17:02 PM, Luca Berra wrote:it would conflict with epochs set for other purposesIt would be nice if packages would include an implicit epoch tag, so a package build on 9.2 will always be newer than one for 9.1 with the same version and release tags.
Not if all our packages were rebuilt with epoch: <release>.<epoch> tags. This may be a bit extreme though.
we would need to have a predefined macro for this %mkepoch() %{mdkversion}.%{1}
so a packager could use
epoch: %{mkepoch 1} => epoch: 920.1
but epoch is an optional tag, is there any way to force it if packager
forgets? (besides rpmlint i mean)when i backport i usually change the release to 0.release we could have all packages have a release of <distver>.<release>mdk ?
Yeah, actually this is a fix for Buchan's idea...
%mkversion() %{mdkversion}.%{1}%{?2:%{2}}%{!?2:mdk}
Usage:
%version %{mkversion 1} => %version 920.1mdk%version %{mkversion 1 plf} => %version 920.1plf
for this to work an updated rpm with just compatibility macro added should be made available for previous mandrake releases. mklibname is another compatibility macro that would be nice for backporters.
regards, L.
-- Luca Berra -- [EMAIL PROTECTED] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \
