[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Doubts in Sigar packaging

On Wed, Sep 15, 2010 at 03:12:22PM +0100, Tony Houghton wrote:
> Adam Borowski <kilobyte@angband.pl> wrote:
> > Why won't you just use `git --describe`?
> > Depending on your upstream's versioning scheme you may want to stick a
> > tilde somewhere.  For example, if the upstream tagged a branch that is
> > to-be 0.8 as "0.8.0-a0", you'd want to make that "0.8.0~a0".  This way,
> > "0.8.0-a0-1247-gf38ef2b" will become "0.8.0~a0-1247-gf38ef2b" and final
> > "0.8" -- just "0.8.0".
> Don't upstream version numbers have to be without hyphens so that Debian
> can easily distinguish the Debian revision from the upstream? Or is it
> OK, because it takes anything after the last hyphen to be the Debian
> revision?

The latter, Debian revision can not contain hyphens, but the upstream one
is allowed to (Policy 5.6.12).

> To make it absolutely clear that the release is newer than any
> pre-release snapshots I reserve *.0 version numbers for pre-release
> snapshots and use *.1 for release, so in your example I'd have 0.8.0*
> for snapshots and then 0.8.1 for release. Then I would use 0.8.1-* until
> releasing 0.8.2, then 0.9.0* for testing a major new feature to be
> released in 0.9.1.

Then it's a bit nicer for you -- you don't need to bother with tildes.
Most upstreams use versions like 1.0pre23 followed by 1.0, which does not
sort properly.  The tilde is a hack to deal with such cases.

1KB		// Microsoft corollary to Hanlon's razor:
		//	Never attribute to stupidity what can be
		//	adequately explained by malice.

Reply to: