On Tue, Jun 19, 2012 at 04:04:31PM +0200, José Luis Segura Lucas wrote: > repository but not still in a numbered version, so, I tried to use the > latest known version and add a ~TIMESTAMPgit... to the minor version > number, but debuild warns me about the version 0.1.0~2012......git-1 is > less than 0.1.0.
Use A~B only if this version should come before A - that is, for example, if
you expect the next upstream release to be A. In your case, use A+B so the
version comes after A in version order.
> The latest thing is that I have seen several packages with ~TIMESTAMP
> (screen, by example): they add a alpha-numeric string after the "git"
> word... what does it mean?
It's the beginning of the hash git uses to uniquely identify the version.
You can see the full hash in, for example, git log, at the beginning of each
patch:
commit 2ff04fd5a95f36497bc8e8c6e44d70c474384ec2
Author: Antti-Juhani Kaijanaho <antti-juh...@kaijanaho.fi>
Date: Mon Jun 18 23:26:59 2012 +0300
Add install-sh
Signed-off-by: Antti-Juhani Kaijanaho <antti-juh...@kaijanaho.fi>
In this case, the hash is the long string after the word "commit"
on the first line, and I would use for example 2ff04 in the version number if I
packaged this version as a git snapshot.
> Where can I found some information about
> packaging directly from VCS?
git-buildpackage has excellent docs. You don't have to use the tools but they
help.
--
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/
signature.asc
Description: Digital signature
