On Mon, 19 Mar 2007, Michael Schwendt wrote:
It still fails for branch-specific (i.e. dist-specific) fixes, where
the
least-significant portion of the full %release value is increased for
rebuilds or minor fixes:
foo-1.0.0-2.el5.fdr.1 < foo-1.0.0-2.el5.rf
but foo-1.0.0-2.el5.fdr < foo-1.0.0-2.el5.rf so it wouldnt be installed in
the first place if you had those repos configured ...
priorities plugin solves that one
but I agree it isnt a 'nice' solution for end users ...
It could be mandated that repotag always comes last and is preceeded by a
(default 0) build id
eg foo-1.0.0-2.el5.1.fdr > foo-1.0.0-2.el5.0.fdr
Surely what really needs to happen for this to work to everyones
satisfaction is n-e-v-r-t
Lance
--
uklinux.net -
The ISP of choice for the discerning Linux user.