Message: previous - next
Month: December 2011

Re: [trinity-devel] Packaging naming with GIT

From: Darrell Anderson <humanreadable@...>
Date: Sun, 25 Dec 2011 14:00:10 -0800 (PST)
> I use this:
> arts-trinity - 4:14.0.0-0debian0+r49+pr4~wheezy
> 14.0.0 is the TDE version, 0debian0 is Debian specific and
> normally
> increments on any required rebuilds, r49 is the TDE source
> revision of the
> arts module, pr4 is the Debian packaging revision of the
> arts module, and
> ~wheezy is the distro version's codename.

I see the release version is three numbers. GIT versions will change daily, but if the official release number changes does that mean official tarballs will be released too?

Version 14.0.0: new tarballs
Version 14.0.1: new tarballs
Version 14.1.0: new tarballs

Only developers and testers will be concerned with the GIT release numbers?

I'm thinking packagers should avoid using the GIT version in the package name if the package is built with an official tarball release.

Official tarball releases:

GIT packages:

Users then know that packages with GIT versions are unofficial testing packages and not official releases.

Sound good?