On Fri, Feb 24, 2006 at 10:50:54AM -0400, [EMAIL PROTECTED] wrote: > A newly created "add patch type" patch depends on all extant "add patch type" > patches. Anytime you have two "add patch type" patches which were > independently developed then they conflict and a programmer is required to > specify how they commute past one another in order to resolve the conflict. > > ;-) > > Regards, > > Zooko > > P.S. I'm not entirely sure if I am serious, but I want to know where this > leads!
I think it's a nice idea to put patch types in patches. Then one would never have to bother with getting the right version of darcs; if I want to pull Crazy patch from Crazy inc.'s repo I'd get their Crazy patch type by dependency rules, and it would nicely be confined to that particular repo so I don't end up creating crazy patches in other repos. To handle commutation rules with conflicts looks like a very simple solution, and practical in that one wouldn't have to "fix" things until they must be fixed, which in practise may turn out to be very seldom. I still thing patch types should be fully declared and hook into both darcs diff and commute functions so that darcs can suggest the new patch types in the record dialogue and commute them with all other patch types. I haven't dared to approach the thought of if any of this is realizable though. :-) -- Tommy Pettersson <[EMAIL PROTECTED]> _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
