[darcs-users] Centralized Darcs usage

[zooko at zooko.com]

> I actually ment that I would like to extend Darcs with this feature (I
> don't really care if it is integrated into the mainline or not). For
> instance, Mercurial makes it pretty easy to add such extra features,
> when customization is required.
> 
> Is Darcs able to be easily extended ?

The problem is that the users do not take any action which darcs, or
extended-darcs, could detect in order to know that they are editing a file.

If they *do* take such an action, then yes, one could easily hack this kind of
feature.

> > I mean that people are expected to use darcs to transfer patches from the
> > separate project repositories into the unified all-in-one repository, and they
> > are expected not to use darcs to transfer patches from the unified all-in-one
> > repository into the separate project repositories.
> 
> The problem here is that in this process, the "unified all-in-one"
> repository would contain the "stable development version" of all
> projects, as opposed to the individual projects repositories that
> contain "possible unstable development versions".
>
> For instance, let's say I have three projects : P1, P2 and P3. Each
> project has its own repository (RP1, RP2, RP3), and each of this
> repository gets integrated into a big central one (RC) periodically (say
> each day).
> 
> Developers of a particular project (P1, P2, P3) will usually first pull
> from the project repository (RP1, RP2, RP3), do the changes, and then
> push back changes to RP1, RP2 or RP3.
> 
> At the end of each day, RP1, RP2, RP3 are integrated into RC -- which
> should usually go well. However, if a problem occurs, we could be in the
> situation where RC is not completely in sync with RP1, RP2 and RP3,
> because the latest changes in any of one breaks something (ex: API
> change in RP1 that makes P2 brake).
> 
> 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.
> 
> I should also add that at some point, changes in RC will be pushed to a
> "production repository" R.

That kind of workflow is easy to implement using darcs.

Regards,

Zooko