On Mon, Aug 17, 2009 at 13:18:52 +0200, Miklos Vajna wrote: > > I wonder if you can trivially prevent application of setpref patches by > > making it inaccessible to Darcs, e.g. > > > > chmod 1755 _darcs/prefs > > chmod 0 _darcs/prefs/prefs > > sudo chown root:root _darcs/prefs/prefs
> The question is if the result will be a consistent repo or not. I > remember that when an 'rmdir' hunk type was applied where there were a > few untracked files, then old darcs versions just left the repo in an > inconsistent state and one had to run darcs repair to fix it. Darcs 2 is much better about this (at least with hashed repositories) because it uses a notion of 'tentative' pristine and inventories to ensure atomicity. So yes you should still have a consistent repo (at least as far as the pristine cache is concerned, which is what matters most here). If I remember correctly this mechanism somehow also makes for a performance regression but a necessary one. Also a happy accident about setpref patches is that darcs is completely stupid about them. It doesn't do any sort of consistency checking whatsoever. You could just delete or overwrite it by hand and darcs would be none the wiser. This property may come in handy for this sort of situation. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpjGWflNfzpr.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
