Re: [Iverilog-devel] Add git commit information to version strings

[Larry D. <ldo...@re...>]

On Mon, Apr 07, 2008 at 09:03:49AM -0700, Stephen Williams wrote:
> Yes, this is a little awkward. When I make a tagged snapshot, that
> file contains so Makefile, but does contain the configure scripts.
                ^^no
> There is an "auconf.sh" script that generates the configure and a
> few other files. There is no "git" context in that case.

This is a great discussion, and welcome progress.
I do second Steve's concern that the snapshot process be
better supported.

I often make snapshots for my internal use.  My process used to be:

cp -a verilog /tmp/verilog-foo
cd /tmp/verilog-foo
rm -rf .git
sh autoconf.h
rm -r `find . -name autom4te.cache`
cd ..
tar -cvzf verilog-foo.tar.gz verilog-foo

but the latest git version string patch broke this.

I'm getting more comfortable working within the original git
tree [*], so I could imagine replacing the copy and rm .git
step with an in-place "tar --exclude=.git".  And having
a proper version tag in the result would certainly be nice.
Then a tidy-up step would be added at the end:
  rm `find . -name configure` lexor_keyword.cc version.h

I humbly request that a sensible way to make such a snapshot
be found, documented (scripted?), and close to what Steve does
for his public snapshots.

One more thing: the current version of version.h handling
breaks the write-protected pristine-source build concept.
The reference source tree should not be touched with an
out-of-tree configure/make.

       - Larry

[*] git bisect rocks!