Re: Documentation of original source tarballs
> > As much as I remember dbs, that one is able to solve this problem: just
> > put the original tarball and the new/modified binaries inside the debian
> > .orig.tar.gz, and you're all set - dpkg-source will not scream about
> > modified binaries in diff.gz since there are none. diff.gz would only
> > contain debian/ which is all text.
> At that point, though, you've modified the original sources, which
> means there's no longer a concept of "pristine source."
Well, there is a pristine tarball embedded in the debian .orig.tar.gz...
Though, you're right, .orig.tar.gz wouldn't be pristine then.
> My personal solution of solving this problem is to simply use a
> debian-native packaging format, since arguably by work-in-progress
> releases are really engineered and tested on Debian first, and then be
> done with it. Some folks kvetched at this approach, however, but I
> really think it's for the best.
If I'll ever face a situation, I'll probably go with uuencoding the
patch and apply it with dpatch, so that I can have the original upstream
tarball as my .orig.tar.gz. Unless I need to _remove_ files, I think
this - or similar - method serves the pristine source way best.
Anyway, just my two HUFs before sleep.