Hi! On Thu, 10 Nov 2011 15:43:04 +0100, l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) wrote: > I agree that ‘git-version-gen’ is the way to go
I won't object. > (there’s no licensing > issue since it’s a build tool.) But we'd include the file in the GNU Hurd/Mach/MIG source tress? Doesn't this affect the license of the whole packages then? > The change is basically two-fold: > > 1. http://git.savannah.gnu.org/cgit/guile.git/tree/configure.ac#n31 > 2. http://git.savannah.gnu.org/cgit/guile.git/tree/Makefile.am#n76 How does this work if a new release is to be made? I first have to tag the Git tree to get a proper version number, I guess? But it's not too much of a problem, as the tag can stay local (and be modified further on, if it was tagged wrongly, or there are any last-minute fixes), as long as the release is not made public. Grüße, Thomas
pgpLOlThZB3RY.pgp
Description: PGP signature
