Re: Centralized darcs

[George Danchev <danchev@spnet.net>]

On Wednesday 02 August 2006 16:34, John Goerzen wrote:
> On Wed, Aug 02, 2006 at 11:23:31AM +0200, Thijs Kinkhorst wrote:
> > On Tue, 2006-08-01 at 16:47 -0500, John Goerzen wrote:
> > > I do use darcs to track patches against upstream.  I really don't
> > > understand the whole cdbs/dpatch/whatever thing -- why use a hack to
> > > manage your patches when you could use a real VC tool that does it
> > > better?
> >
> > A patch system can be very convenient for the people who are not the
> > maintainer of the package - if you fetch the source package from the
> > archive you get all packages neatly separated and mostly with a
> > description. It's then easy to extract a patch, disable a patch or add a
> > new one, for example when NMU'ing.
>
> Actually, I disagree with that.  I always hate having to work with a
> package that uses a patch management system, because then I have to
> learn the system before I can do any work on the package.  And there are
> several systems.  Plus it's not always quick & easy to generate a diff
> for an NMU out of that.  And the resulting diff isn't necessarily easy
> to read (being a diff of a diff).

How is that not true if one knows a given patch system and does know about 
your VCS and needs to work on one of your packages. Do they have 
debian/patches/ as separate file, how do I know how to update/remove/etc 
them ? How is that different from learning darcs patch system which might 
happend to be new for me. There is also git arch which also pretend to be a 
patch system at heart. Thus the diversity is the same as in different patch 
system / not necessary a bat thing though /.

> > If I'm correct the source package won't display the changesets from your
> > VC.
>
> That is correct, per Debian policy.  However, if you're just NMUing,
> presumably you wouldn't care about that -- you'd send me a diff, which
> would then become a changeset in my VC tool.
>
> -- John

-- 
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB