Thanks all for your ideas. I realise I was kind of stuck in my thinking. Your suggestions made me think about the problem in a different way. I think i have a solution now.
The main use of the in-file version numbers was not for me while editing the file. It is used when I email source to co-authors who do not use version control. When an edited text returns, i need to know what revision they made their changes too. This info can be easily inserted into the file (and file name) before emailing. Regarding the version info for the PDF, I think the simplest solution is a line like this in the makefle darcs info --show_useful_info | text2pdf | pdftk stamp (*) this stamps the repository's useful information on the top of every page and avoids the (sometimes messy) svninfo package altogether. (*) actual command is more like darcs info --show_usefull_info | text2pdf -A4 -v0 -l1 | pdftk $@ stamp - output s$@ Thanks for the ideas! Niall Murphy On Sun, Mar 14, 2010 at 9:00 PM, Guillaume Hoffmann <[email protected]> wrote: >> I think the canonic solution to this, at least in program repos (as >> opposed to document repos) is to extract version information into a >> separate header that is included in the main source (instead of inline >> version info in the version-controlled data). > > That's what I wanted to say but you worded it much better than me, > thanks Petr :-) > > guillaume > _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
