[darcs-users] Post-hook freeze under darcs-unstable mingw compile

[Max Battcher]

On 5/26/07, Kurt Granroth <darcs-users at granroth.org> wrote:
> Ah.. that's a good point.  I was (perhaps naively) assuming that the
> posthook command was run on every file in the repository.  Your
> description makes it sound like these two sequences are identical:
>
> Sequence 1:
> $ darcs get --posthook=unix2dos --run-posthook user at repo
>
> Sequence 2:
> $ darcs get user at repo
> $ unix2dos

Yes, that is the case.

> Er.. but that would assume that the posthook was started *inside* of the
> repo directory.  Is the posthook command given any parameters?  Like say
> the name of the repo working directory?

The posthook should have the same working directory as the repo
working directory, I believe.  The posthook is given no parameters
right now.  There have been some ideas for parameters to pass and I
believe the general idea was to pass any and all posthook parameters
as environment variables.

Don't forget that you can use ``darcs query manifest`` to get the list
of darcs-controlled files, and I'd recommend not touching anything
under _darcs or you'll risk repository corruption.

-- 
--Max Battcher--
http://www.worldmaker.net/