repotag in EPEL

[Fernando Lopez-Lezcano]

On Fri, 2007-04-27 at 15:57 -0400, Matthew Miller wrote:
> On Fri, Apr 27, 2007 at 12:46:26PM -0700, Fernando Lopez-Lezcano wrote:
> > > Alternately, the repotag should be _hard coded_ in the spec file. (For
> > > better or worse.)
> > The reason for not hard coding it is that not doing that enables the
> > same spec file to be used for both epel and extras (or now, fedora). 
> 
> So, uh, how does it differ from the dist tag at that point? It ends up
> meaning the same thing.

disttag: 
    version of the distribution the package was built for.
    value common to all repos that build for the same distro version.
    does not say anything about where the package comes from.
    (it is useful to have it even in the core distribution)

repotag: 
    repository the package comes from.
    unique value for each repository.
    value common to all packages in a given repository.
    does not say anything about the version of the distro the package
    was built for. 

Within a spec file the release tag is appended with either (current
usage):
    %{?dist}
expanding to ".elx.epel" or ".fcx"
or (suggested usage):
    %{?dist}%{?repotag}
expanding to the same thing. 

See Jeff Spaletta's email in this thread for a very very nice
explanation of why it exists, how it is done today and potential future
directions. 

-- Fernando