Re: How to handle Debian patches
On Friday 16 May 2008, Joey Hess wrote:
> Raphael Hertzog wrote:
> > I totally agree that we need to make our changes more visible. In the
> > openssl case, the patch in question is inside the .diff.gz and you don't
> > notice it in the unpacked source package. I tend to give a look to what's
> > in debian/patches/ when I rebuild a package but not to what's in .diff.gz
> > only.
> > To me this one proof more than even when VCS are used to maintain
> > packages, our source packages must clearly identify the Debian patches
> > that are applied.
> You're insinuatiog that a VCS does not allow easily browsing and
> examining patches, and I just don't buy it.
This is true, but not always handy. What you might buy is that the upstream or
resp. debian user is not supposed to know for your kind of VCS (having it
installed, etc) and where to find your VCS repo -- a ftp'ing of diff.gz or
apt-get source pkg should be enough to get the *clearly identified patches*
to the upstream source tree.
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