zooko wrote:
> Here's what I recommend, and what I've been doing for months, both
> with the large Tahoe code base -- http://allmydata.org/trac/tahoe and
> with numerous smaller codebases -- http://allmydata.org/trac .
Hey Zooko, your recommendations are interesting... Did you read my blog
post on the subject? I thought I might summarize some of my differences
to your opinion, just to add them to the discussion:
I recommend always using hashed repositories for working repositories
with darcs 2, particularly for new developers, because hashed pristine
alone removes a lot of frustrations and simple confusions that darcs-1
format has. (I think we all have too many stories of repository
corruption from "Whoops, you mean I wasn't supposed to touch the version
under _darcs/{current,pristine}?" in it's many forms.) Yes, it's a
little slower, but IMO the speed difference is usually worth it. (As
long as you aren't using a GHC 6.8.2-built darcs, and even sometimes
then depending on the project...)
I recommend using darcs-2 format for new projects and I think that there
are also good opportunities (such as just after a big release) for
existing projects to move to darcs-2 format. At the very least, new
projects shouldn't have to put up with old sorts of conflict failures
that darcs-2 format should eliminate.
--
--Max Battcher--
http://www.worldmaker.net/
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
