What is the correct way for script darcs?

I have several different darcs repositories, and I would like to write a script to automatically make changes from these repositories at the end of the day. I read in this thread that the "correct" path to script darcs uses a library. But here http://darcs.net/Library says that "this is a very big job" and does not have a stable API. What is the "correct" path to script darcs.

+5
source share
1 answer

This is great for the darcs daily command script, like any other command line program. It is also great for darcs interactive script commands, but where it gets fragile because these interactive hints are updated and change frequently in newer releases of darcs. Therefore, if at all possible, make the command non-interactive, for example, using the -a / - all flag. Clicking and pulling is easy, here is a regular click that I run from / etc / crontab:

*/15 * * * * darcsden  cd /home/darcsden/darcs/darcs-reviewed; darcs pull -a http://darcs.net/reviewed >/dev/null # 2>&1

but watch out for things that can prevent successful non-interactive push or pull:

  • conflicts, especially with unrecorded changes
  • Incorrect file / file / file permissions
  • stray _darcs / lock file remaining after abnormal completion
+5
source

All Articles