Hi Claus, I'm redirecting this discussion to the darcs-users mailing list where it belongs. :-)
On Tue, Sep 09, 2008 at 01:46:30 +0100, Claus Reinke wrote: > You mean because it encrypts file names in pristine? More or less. > I never liked that idea, I must say - if the hashes are useful, why > not store them out of the way? Having a real pristine copy of the repo > in place was a big point in favour of darcs1: (a) it is unlikely that > it would screw up both copies at once, (b) it allows for easy > scripting and tool access bypassing darcs. Please have a look at http://bugs.darcs.net/issue230 for background to this decision. Relying on a real pristine copy (which darcs 1 has done) made darcs vulnerable to pristine corrpution, because it would sometimes be accidentally modified by third party tools like Eclipse or Unison. I like the hashed pristines because (1) files which are introduced by third party tools are ignored because they do not appear in the index and (2) modifications to pristine files can be detected through hash failure and (3) relying on darcs-internal filenames avoids the case sensitivity issue as well as http://bugs.darcs.net/issue53 In any case, I do not believe this is a design question which we will be revisting shortly, as we are focusing on the performance issues first. In the meantime, there are various ways to retrieve the pristine version of a file, either by use of darcs diff (--diff-command "cat %1") or via the 'show contents' commands. > Anyway, I thought I'd give it a try but, geez, that is slow! 20 > minutes wall clock time before it even starts "writing inventory"? > Hogging all my memory and then some? No thanks. I'm not sure I'm going > to wait around to see it finish. You may be interested in http://bugs.darcs.net/issue973 On non-Windows machine, Petr Rockai have identified the slowness as being due to a library bug in GHC 6.8.2 (since fixed in 6.8.3). The workaround is to compile darcs with GHC 6.8.3. That said, these findings apparantly do not translate to Windows. If we had more Windows-based developers, it would be useful to to have one of them investigate the cause of this. Suggestions would be gratefully received, ideally in patch form, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpSqyFUYkbjV.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
