Hi Ralf,
Ralf Wildenhues wrote:
You could then experiment with suitable rules to keep the file up to
date, depending on the VCS. VCS hooks could ensure to update (or
remove, or otherwise outdate) the file. All rules that need the version
can just depend upon the file, and read from it afterwards, that nicely
avoids any duplicate work. The file should conceptually live in the
source tree as it is a source property not a build one (though newline
encoding may make this a bit ugly for cross-platform mounts).
Maintainer mode could even be used to avoid updates to this file.
What do you think of this approach?
I think that is an excellent direction and it is fairly easy to
propagate that information into a `version.c' or similar file. However,
I wonder if it's possible, using this approach, to also override
$(VERSION) (or dirstdir) in the Makefile?
Thanks,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
