On Nov 20, 2008, at 16:21, Trent W. Buck wrote: > On Thu, Nov 20, 2008 at 10:15:51PM +0900, Stephen J. Turnbull wrote: >> Instead of layering (totally ordered) branches over Darcs, why not >> explore the possibility of naming subsets of the repo (while >> respecting the preorder)? Maybe you could (eg) "block" a patch from >> being pulled (cf http://www.orcaware.com/svn/wiki/Svnmerge.py). You >> could do things like create "features" as a subset of patches. "Add >> up" the features to configure your app! >> >> This is already implicit in patch theory as I understand. What >> Darcs doesn't provide yet is a powerful, simple way to name and >> manipulate these subsets, except in a clumsy way be creating a new >> repo. > > +1 > > Could we (easily) get some of the way to this by allowing "darcs tag" > to select patches to include in the tag? >
Yes, yes, yes. But it gets a little more complicated then that because you need to make sure you don't record patches that create dependencies between "features" (hereafter modules).... otherwise modules can't be cherry-picked the way you want. I'm just about finished hacking up a presentable implementation of this concept as a warper around darcs that enforces and automates practices needed to maintain a modular repository. Regards, Ben Coburn _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
