My thoughts on repotag
Michael Schwendt
mschwendt.tmp0701.nospam at arcor.de
Mon Mar 19 17:12:50 UTC 2007
On Mon, 19 Mar 2007 11:52:17 -0500, Tom 'spot' Callaway wrote:
> On Mon, 2007-03-19 at 13:50 +0100, Dag Wieers wrote:
>
> > It makes not difference what the release is. Whether it influences the
> > release comparison or not, releases cannot be compared between
> > repositories. There is no relation.
>
> Alright. So, I was under the assumption that repotag was being used to
> compare packages between repositories. This is apparently not the case.
>
> Can you reiterate the actual problem that we need to solve here? :)
>
> It may turn out that using a repotag solves a problem, but I'd much
> rather approach the problem before arguing about the solution.
The repotag is supposed to be a human-readable repository identifier in
the package NEVR.
Its sole purpose is in aiding users in choosing the right bug tracking
system where to report problems with a repository's packages during
a repository mixing scenario.
The side-effects and consequences of extending %release are ignored. It's
called a trade-off without interest in the alternative solutions like
"Vendor:".
More information about the epel-devel-list
mailing list