[darcs-users] Centralized Darcs usage

[Tommy Pettersson]

On Fri, Apr 21, 2006 at 11:21:20AM -0400, Sébastien Pierre wrote:
> So basically, most developers will want to pull out projects from RC,
> while RP1, RP2 and RP3 are only for developers actively working on P1,
> P2 or P3.

RC contains patches from all of P1, P2 and P3, and it is not
possible to automatically select only patches from one of them
(but it will be when a keyword 'touching' for the --match
options is implemented). To pull patches from RC to any of RP1,
RP2, RP3, or to create a new branch for a subproject, you'd have
to manually answer no to all "other" patches in RC not belonging
to Px.

If all subprojects are started with a patch that adds an empty
project dir, you'd only have to answer no to these addir patches
for non-relevant projects, and dependencies will take care of
the rest. Giving these addir patches visible easy to spot names
helps.

There could also be a hierarcy of subprojects:

_darcs
 \_ A-projs
 |   \_ proj-1
 |   |  ...
 |   \_ proj-11
 |  ...
 \_ W-projs
 |   \_ proj-143
 |   |  ...
 \_ X-projs
 |   ...

Then answering 'no' to A-projs will skip a whole bunch of
subprojects.

If more than one subproject is "checked out" in one working
branch, there is no automatic way to pull in new patches from RC
for just one of the subprojects; you must look at the file paths
in the contents of each patch (until --match 'touching foo' is
implemented, which will automatically check and match file
paths).


-- 
Tommy Pettersson <ptp at lysator.liu.se>