Re: Centralized darcs
On Wednesday 02 August 2006 20:11, Otavio Salvador wrote:
> Frank Küster <email@example.com> writes:
> > George Danchev <firstname.lastname@example.org> wrote:
> >>> > 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
> >>> that?
> >> 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.
> > Not only that. Many packages make changes to upstream files that are
> > Debian-specific (e.g. for using infrastructure or libraries that don't
> > exist outside), but also changes to upstream files that will/should be
> > temporary because upstream will apply the same patch, has been asked to,
> > or the patch has been taken from their development version.
> Iff we use a branch to each change we can have same behaviour using a
> SCM but anyone that would want to change or contrib changes will need
> to learn how we deal with this all.
This is fine, but (again) you forget about your 'apt-get source' users, which
are not supposed to be aware of your SCM, where your repo is, patches applied
to the upstream source and why they have been applied. I.e. if you have
patches, do them debian way (using a debian patch system) even using SCM to
manage your whole packaging. Your orig.tar.gz must be really original tar.gz,
and your diff.gz should hold whole debian-specific thing.
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