On Fri, 2006-06-16 at 16:49 +0200, Ralf Corsepius wrote:
On Fri, 2006-06-16 at 08:55 -0500, Tom 'spot' Callaway
wrote:
> On Fri, 2006-06-16 at 15:39 +0200, Ralf Corsepius wrote:
>
> > > The guidelines also mention that use of %{?dist} is optional and not
> > > necessary in _any_ package.
> > One of the unclearnesses I don't find helpful.
> >
> > At the moment, we have various styles of release tags, which all are
> > incompatible and without any guarantee of a clear upgrade path ...
>
> In Core? Yes.
Some random examples:
..
ant-antlr-1.6.5-1jpp_9fc.i386.rpm
..
dmraid-devel-1.0.0.rc11-FC6.i386.rpm
Time to file bugs. ;)
> In Extras? No.
Yes. There exist packagers who (In FE devel)
* don't use %{?dist} at all
* some use N%{?dist} and increment N with each iteration.
These are correct...
* some use N%{?dist}.M and increment M with each build-iteration
...and these are not. More bugs to file!
Well, on one hand you told "Same packaging conventions in FC as
in FE",
the other hand you are telling "%{dist} won't ever be in brew".
Both FC and FE have the option of using a dist tag. In FE, we have a
nice macro thanks to our super awesome buildsystem. In FC, they don't
have a nice macro. Rules are the same. If you use a dist tag, it has to
meet the syntax as documented in the guidelines.
=> project has failed even before it started?
> There are lots of areas where core will have to improve to meet the
> guidelines, and none of them will happen over night.
Well, I'd put NEVR conventions on a top priority item on the agenda.
Seems like a valid point to me. This should be something that isn't
difficult to audit, possibly even via automated script. Jesse, is this
something that could bootstrap into Brew?
~spot
--
Tom "spot" Callaway: Red Hat Senior Sales Engineer || GPG ID: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader:
http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!