On Fri, 06 Jan 2012 15:12:41 +0100 Tobias Frost <t...@frost.de> wrote:
> Am Donnerstag, den 05.01.2012, 13:30 +0000 schrieb Tony Houghton: > > > The debian packaging and upstream are in one repository and I didn't > > want the contents of the release tarball to be inconsistent with > > what's in the package. I would also have to change the way I use > > git tags to generate a version number dynamically. > > I do it that way: > I use a dedicated git branch for the debian stuff, containing the > the debian stuff (and the source, but source is not edited in this > branch) > The developement (on the source) is done in a different branch and > whenever I want to make a debian package I just merge the latest > source into the "debian branch". That sounds like a good idea, I'll probably do it that way. > This way your tricks with git-tags could still work. (Anyway, can you > elaborate on this, as I am curious about this idea) When I'm about to do a release I tag it with the release version number. The build system uses git describe to generate a version number (with autoconf I did it in the bootstrap.sh by generating configure.ac from configure.ac.in, maitch does it in the configure phase), only converting from the format 2.4.0-1-g1234abcd to 2.4.0.1~g1234abcd. That way anything built between releases has a meaningful and uniquely identifying version number. I also use tags of the form x.y.0 when I add a new feature or set of features, so that versions with a .0 are testing versions for the next release x.y.1. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120107133650.0f0c2449@junior
