Re: Centralized darcs
On Wednesday 02 August 2006 18:35, John Goerzen wrote:
> On Wed, Aug 02, 2006 at 06:01:27PM +0300, George Danchev wrote:
> > > > 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
> > >
> > > They just apt-get source, hack away, and send me a diff.
> > Also true for any debian patch system, but with the gain the debian
> > specific
> No, it's not, because for most of them, the "source" that you get with
> apt-get source is a tar.gz file and a debian/ directory. You can NOT
> just hack away on that like you would any package. You MUST learn the
> specific tool to do ANYTHING.
After apt-get source you get debian source package directory with
debian/patches/ inside. Learing to add/remove/update patches is easy and if
one is not able to learn that, better not to send any diff, waste of time.
> > > They shouldn't be converting the package to use a patch system.
> > They can send new patch to be included in debian/patches/, remove one, or
> If I am using darcs, or svn, or whatever, there is no debian/patches at
> all. I don't understand what you are saying here.
Where are you debian specific patches you apply to the upstream source tree as
patches in debian/patches/ do. Or your have orig.tar.gz already patched with
these and which is no more original tar.gz, and diff.gz not containing these.
This is forbidden by the policy as we know. And this adds confusion.
> > But you lose debian specific patches to be clearly separated from the
> > upstrem source (digging diff.gz for that is not fun), unless one knows
> > where to find
> First, what is a "Debian-specific patch?" Isn't everything in diff.gz
Right, but you have parts which touch upstream files (debian/patches/*), and
parts which does not (debian/!patches). I prefer them to be clearly separated
when the whole debian source package is unpacked.
> Maybe you mean just stuff in debian/. Well it's easy enough to filter
> that out.
> I think people that are NMUing packages rarely care about this.
Note that I'm not against distibuted VCS (obviously), I argue that no matter
which VCS is used, IMO debian specific patches which alter upstream source
should be clearly separated (these are debian/patches/* in the world of
debian patch systems).
<second try/>Please, do not CC: to me. I didn't explicitely requested that, it
is obvious that I'm subscribed to this list.
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