kismet and svn builds?

[Tom 'spot' Callaway]

On Thu, 2005-05-19 at 12:09 -0400, Chris Ricker wrote:

> 3. kismet support for ipw2200 cards requires a build from the kismet 
>    development svn tree. How does one package a cvs / svn / etc. checkout 
>    for FE? Or is the answer just "don't do that" :-)

We're still trying to figure that out.

Right now, I think this is the wording I've got so far. Please point out
flaws in this.

Non-numeric versioned "pre-release" and "post-release" packages can be
problematic so they must be treated with care. These are cases where the
upstream "pre-release" version has letters rather than simple numbers in
their version. Often they have tags like alpha, beta, cvs, svn, rc, or
letters like a and b denoting that it is a version before the "final"
number. Unfortunately, we cannot simply put these letters into the
version tag, so we'll use the Release field for this. 

Release Tag for Pre-Release Packages: 

        0.%{X}.%{alphatag} 
        
Release Tag for Post-Release Packages:

    %{LastMajorRelease}.%{X}.%{alphatag}

Where %{LastMajorRelease} is the build number from any previous "stable"
package builds (if none, use 1), %{X} is the release number increment,
and %{alphatag} is the string that came from the version. In this case,
the period '.' should be used as the delimiter between the release
number increment, and the non-numeric version string. No other extra
characters should appear in the Release field. This is to prevent
Release values such as "3jpp_2fc.42-spotwashere". When using CVS/SVN
checkouts, use an alphatag of the format:

    YYYYMMDDcvs

Where YYYY is the digits for the year, MM is the zero-padded digits for
the month, DD is the zero-padded digits for the day, and "cvs" is the
type of checkout. The date in reference is the date that the checkout
was taken.

In the post-release case, 

Example (pre-release): 

     mozilla-1.4a.tar.gz (this is a pre-release, version 1.4a of mozilla)
     mozilla-1.4.tar.gz (this is what the 1.4 release will actually look like)
     mozilla-1.4-0.1.a  (so, this is the acceptable Fedora %{name}-%{version}-%{release})
     mozilla-1.4-1 (and this is what the 1.4 release Fedora %{name}-%{version}-%{release} should be)

Example (pre-release svn):

     kismet-0.1.20040110svn (this is a pre-release, svn checkout of kismet)
     kismet-0.2.20040110svn (this is a bugfix to the previous package)
     kismet-0.3.20040204svn (this is a new svn checkout, note the increment of %{X})
     kismet-1.0-1 (this is the formal release of kismet 1.0)

Example (post-release cvs):

     kismet-1.0-1 (this is the formal release of kismet 1.0)
     kismet-1.0-2 (this is a bugfix build to the 1.0 release)
     kismet-1.0-2.1.20050515cvs (move to a post-release cvs checkout)
     kismet-1.0-2.2.20050515cvs (bugfix to the post-release cvs checkout)
     kismet-1.0-2.3.20050517cvs (new cvs checkout, note the increment of %{X})

~spot
-- 
Tom "spot" Callaway: Red Hat Sales Engineer || GPG Fingerprint: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader: http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!