There has been discussion from time-to-time about how to pass patch
and/or file information to a posthook command.  If I recall correctly,
the dominant opinion is that this information could be supplied in an
environment variable.

My workaround is currently to run a perl script to find patches with a
recent update time, and write those to a file:

  apply posthook /usr/local/bin/applied_patches.pl 15 > _darcs/prefs/applied_patches; /usr/local/bin/applied_patches.pl --files 15 > _darcs/prefs/applied_files
  apply run-posthook

I would love to have the hashes of each affected patch in one
environment variable, and the names of each affected file in another
environment variable.  They could be called something simple like:
DARCS_PATCHES and DARCS_FILES, or have HOOK or POSTHOOK in there
somewhere if we want to get fancy.

I am attaching my perl script 'applied_patches.pl' as an example of
what I am doing.  It is barely sufficient for what I am currently
doing, but can very easily give incorrect results.

-kolibrie

Attachments

• applied_patches.pl

or you can just alwasy store the hash of the last patch. this is what we use in
darcs-hooks (a generic framework, currently contains 3 patches):

http://ftp.frugalware.org/pub/other/darcs-hooks/

(sorry for changing the priority, i had to do so to be able to answer)

kolibrie,

This issue sounds like a dupe of issue639, which you reported more recently, so
I'm marking it as such. Please re-open it if I'm wrong.

On Sat, Feb 09, 2008 at 05:37:30AM -0000, Mark Stosberg wrote:
> This issue sounds like a dupe of issue639, which you reported more recently, so
> I'm marking it as such. Please re-open it if I'm wrong.

I did not report issue639, but it does appear to be talking
about the same solution, so we can say they are duplicates.

-kolibrie

This is now considered "resolved-in-unstable", since the dupe of it is:

http://bugs.darcs.net/issue639

DARCS_PATCHES and DARCS_PATCHES_XML are now exported to address this. The manual
was updated accordingly.