I haven't updated darcs for long now, due to the difficult installation,
so I have still darcs-1.0.3.

The behaviour of 'darcs setpref test' in this version is not correct I
believe: When I change the 'test' command, but do not record that change,
the modified repository is tested with the new 'test' command
nevertheless. I think that the repository must be tested with the test
recorded in the repository.

Hi,

Thanks for your comment.  For the record darcs 1.0.8 still behaves this way and
likely 1.0.9.  But why is this incorrect?  It seems more consistent that when I
make a change, it affects the current repository, not just the recorded one.  Cf
darcs replace, for instance.

Besides, you can always darcs revert to get the old test back.

In any case, it would really be a good idea to upgrade your darcs if possible. 
 Many bugs fixed in between 1.0.3 and 1.0.9.

Tentatively marking as resolved.  Feel free to respond (and thereby re-open)

On Thu, 12 Jul 2007, Eric Kow wrote:

> Eric Kow <eric.kow@gmail.com> added the comment:
>
> Hi,
>
> Thanks for your comment.  For the record darcs 1.0.8 still behaves this way and
> likely 1.0.9.  But why is this incorrect?  It seems more consistent that when I
> make a change, it affects the current repository, not just the recorded one.  Cf
> darcs replace, for instance.

Consider following scenario: I haven't used tests so far. I setup a darcs
test. The test fails. I resolve this bug and record it.  But the test case
still fails. I can record it with -no-test, but I want to show other
participants of the project, that at this point there is no test, that is
satisfied. Thus test settings and tested program parts belong together.

> Besides, you can always darcs revert to get the old test back.

It's not the problem of getting the old test back, it's only the question
how tests and tested parts are bundled.

Thanks for clarifying that.  Your explanation makes sense to me.

The thing that supports your idea is that the tests are always run on the
recorded version anyway, never the working directory, so in a way, you would
expect only the recorded tests to run as well.

On Thu, 12 Jul 2007, Eric Kow wrote:

> The thing that supports your idea is that the tests are always run on the
> recorded version anyway, never the working directory,

exactly

> so in a way, you would expect only the recorded tests to run as well.

That's it.

> ----------
> priority: not-our-bug -> bug
> topic: +ProbablyEasy

I don't know if it breaks some setups. One should certainly alert people
about this change.

This is the desired behavior.  This is needed if users ever need to edit the
test command according to their local setup--which is why the prefs file is
located in _darcs/prefs, so that users can edit it.  The point of prefs, in
short, is repository-specific preferences.