If I create a local copy with --no-set-default I would expect no to find
_darcs/prefs/defaultrepo but It always appears there with the repository
from which  it was got.
A simple test case for it could be

. lib
darcs init --repo S
darcs get S Q --no-set-default
not find Q/_darcs/prefs/defaultrepo

Attachments

• unnamed

On Thu, Jun 10, 2010 at 22:33:11 +0000, Adolfo Builes wrote:
> . lib
> darcs init --repo S
> darcs get S Q --no-set-default
> not find Q/_darcs/prefs/defaultrepo

Could you send that as a formal test case?
See http://wiki.darcs.net/Development/RegressionTests

Thanks,

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Actually, I need we first need to (action) determine if it even makes
sense in the first place for get to support the --set-default and
--no-set-default flag.

I'm going to submit a patch taking out the flag to get some comments.

OK! That was quick...
Ian said on IRC: There are times I wouldn't want to have the default set
 When I'm making a totally separate branch, and wouldn't want to
accidentally push changes back or forth

so if you could submit that test, Adolfo, I think it'll be an easy fix

The following patch updated issue issue1875 with status=resolved;resolvedin=2.5.0 CURRENT

* Resolve issue1875: avoid accidentally setting default. 
Ignore-this: d03cfc6111805515ae4f1ca467beab2c
Two cases fixed:
 - setting default on dry-run
 - setting default on darcs get --no-set-default

The following patch updated issue issue1875 with status=resolved;resolvedin=2.8.0 HEAD

* Resolve issue1875: avoid accidentally setting default. 
Ignore-this: d03cfc6111805515ae4f1ca467beab2c
Two cases fixed:
 - setting default on dry-run
 - setting default on darcs get --no-set-default