Suppose I run

$ cd myrepo/sub
$ darcs record foo/ bar/ baz.txt

The pre-hook will be executed in the root of the darcs repo.
I'd like to have the search path that the user told darcs to use to find changed
files, to be in an environment variable when running the pre-hook.

DARCS_BLAH="sub/foo sub/bar sub/baz.txt"

The paths are normalized, so that the are relative to the root of the repository.

This would be useful for a QA enforcer in the gentoo overlay.
Knowing the changed files is similar, but knowing what the user asked for is ideal.

On Fri, Apr 17, 2009 at 06:01:53AM +0000, Lennart Kolmodin wrote:
> The pre-hook will be executed in the root of the darcs repo.  I'd
> like to have the search path that the user told darcs to use to find
> changed files, to be in an environment variable when running the
> pre-hook.
>
> DARCS_BLAH="sub/foo sub/bar sub/baz.txt"

Darcs already passes several data via environment variables.  Can
someone confirm that this is not already among them?

On Sat, Apr 18, 2009 at 03:49:56 -0000, Trent Buck wrote:
> > DARCS_BLAH="sub/foo sub/bar sub/baz.txt"
> 
> Darcs already passes several data via environment variables.  Can
> someone confirm that this is not already among them?

I think the issue is that these are passed in for the posthooks, and
unfortunately it's not self-evident how to do the same for prehooks.
(the posthook code is based on the patch contents)

This sounds like it shouldn't be too hard to do.

I might avoid calling it DARCS_FILES (which is what we use for the posthooks)
because this means something subtly different.  DARCS_FILES is based on the
patch contents.

What we want here is something more like DARCS_FILE_ARGS.

Things to watch out for is the path normalisation and also --repodir.