Kai Tietz schreef op vr 13-09-2013 om 11:24 [+0200]:
> HI,
> 
> we had in the past already the idea to add svn-revision-number to
> identify version proper.  See for this in the mingw-w64-crt/ folder
> the header revstamp.h (a side-note ...  actual the place should be
> IMHO instead the mingw-w64-include folder ....).  We would need a
> server for doing this stamping on modification every day as cron-job.
> Sadly we didn't found until now a volunteer which would run such a
> cron-job in a reliable way.
> The idea to use an svn-hook for this, is pretty bad, as it could lead
> to issues about consistency of patches due a hidden commit-conflict
> ... additionally SF has disallowed custom svn-hooks AFAIK.

I've also stumbled across this situation with my own projects (where I
wanted to embed the svn revision in the 'About' dialog). For this I
added a small piece of code to the Makefile.am which automatically
created a small .h file containing the svn revision used (using the
svnversion tool).

At the moment this can't properly be applied to mingw-w64 as some people
(for example us Fedora folks) are using the 'Download snapshot' feature
from the SourceForge SVN webinterface
( http://sourceforge.net/p/mingw-w64/code/ ) to generate SVN snapshots
which automatically strips away all svn administration (and breaks the
svnversion tool).

A pre-commit hook would fix this but isn't really elegant as it modifies
the contents of commits before they're saved in svn.

Regards,

Erik



------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to