> What about doing it in the other direction, that is, giving the > responsibility of inserting the "revision numbers" into your documents > to the build process, instead of darcs ? > The idea would be to use a Makefile that inserts in all your .tex > documents, a header based on the result of "darcs changes --last 1" > for instance. Would it solve the problem for you ?
This has the same downside as my posthook script, namely: - that the source file only contains the correct patch number after a commit (if i want to check out the version with patches up to 135, but then open the file and see "Patch Num: 112" which upon compiling, gets corrected) and more irritatingly (dangerously?) - the files are left modified but unrecorded after a commit. So while this gets something of the required effect it is still a bit unsatisfying. I will try it for a project and see how things go. While I understand that what I want to do is a bit against the theory of darcs, I really love the simplicity of darcs and would love to switch over. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
