[packagers] Smokeping RPM

[Fernando Lopez-Lezcano]

On Tue, 2006-12-05 at 21:40 +0100, Dag Wieers wrote:
> On Tue, 5 Dec 2006, Wil Cooley wrote:
> 
> > On Fri, 2006-12-01 at 12:36 -0800, mchandler at solutions.canon.com wrote:
> > > I was trying to update the RPM I found for Smokeping from 2.0.4 to 2.0.9
> > > and I've run into some problems.  I built the RPM with "rpmbuild -ba
> > > /usr/src/redhat/SPECS/smokeping.spec" and it named it internally and
> > > externally with smokeping.noarch.2.0.9-0.0.%{dist_tag}.%{vendor_tag}.rpm  I
> > > renamed the file and then I noticed that yum kept referencing the old name
> > > internally as variables.  I guess it has an internal spec file inside the
> > > RPM.  I went ahead and used it to upgrade a test server and it looks like
> > > it's working, but I'm not sure what to check exactly.  The binaries are the
> > > same, but I suppose they got updated.  The version # in the webpage for
> > > smokeping changed and it's still working, but I have an uneasy feeling.  I
> > > looked through the spec file and I see where it names those variables, but
> > > I don't see how or where it defines them.  I've search online, but I'm so
> > > new to this that I have no idea where to look or how to search for it.  I
> > > checked out rpm.org and some other linux resources, but to no avail.  Any
> > > ideas?
> > 
> > FYI, he was looking at my spec file, which I've since updated (to use
> > '%{?dist}' instead, like FE) and I've responded to him privately.
> 
> I think we're ready to move to the FE standard now where they include the 
> disttag in the Release tag.
> 
> Should we also include a repo-macro in the release (I am in favor of 
> that). Something like:
> 
> 	Version: 4.5
> 	Release: 1%{?dist}%{?repo}
> 
> Where dist = .el3 and repo = .rf
> 
> I dislike it for the fact that the release is harder to identify (having 
> the % attached to it closely) and I generally feel this should be left to 
> the buildsystem (which knows best).
> 
> Dries, Matthias, what do you think ?
> 
> Anyone else having an opinion on this ?

I'm currently starting to use %{?dist} myself but I'm including the
repository in the "dist" tag itself (set in the build system). 

-- Fernando