My thoughts on repotag
Michael Schwendt
mschwendt.tmp0701.nospam at arcor.de
Mon Mar 19 13:26:14 UTC 2007
On Mon, 19 Mar 2007 13:50:05 +0100 (CET), Dag Wieers 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
>
> Then you assume that minor numbers are behind the repotag, which is a bad
> implementation.
Funnily, that implementation is used by Fedora and has worked well.
The least-significant portion of %release however is blocked by and abused by
a dist tag and a repo tag.
> > In the past, the proponents of mandatory dist tags have ignored that issue
> > or have tried to fight it with their main counter-argument that updates
> > are applied to all branches always. Mass-updates *always*.
> >
> > As I've explained before, more tags at the right of %release don't solve
> > the repository mixing problems.
>
> But it doesn't affect it either. The example you gave was a bad example.
> disttags and repotags are at the far right.
"Highest" repo tag does win RPM version comparison.
More information about the epel-devel-list
mailing list