Re: [PATCH] proposed v3 source format using .git.tar.gz

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Joey Hess <joeyh@debian.org> writes:

> Frank Lichtenheld wrote:
>> This should probably error out. Aren't v3 packages always native in the
>> sense tested here?
>
> Not necessarily. I wanted to leave the option open to use wig-n-pen to
> constuct mixed source packages that maybe use vcs for debian/ and
> pristine source for the rest + a diff.gz, or something like that.
>
> I think the code will basically handle unpacking such a mongrel,
> although there are no tools to create one.
>
> -- 
> see shy jo

Shouldn't we allow any number of any files in the dsc and dpkg-source
would unpack/apply them each in turn. For example you could have:

Files:
 xxxx yyy foobar.orig.tar.bz2
 xxxx yyy images.tar
 xxxx yyy debian.git.tar.gz
 xxxx yyy security.diff.gz

dpkg-source would unpack the orig.tar.bz2 first, then add the
images.tar, merge the debian.git and last apply the security patch.

Dpkg-source should record the files it used to construct a source dir
in debian/something so that subsequent source builds can recreate the
procedure. When building source the last entry should be modified
where possible or a new diff.gz added otherwise. Meaning dpkg should
unpack foobar.orig.tar.bz2, images.tar and debian.git.tar.gz and then
create a new security.diff.gz in this case.

Tools like svn-buildpackage could create a new debian.svn.tar.gz file
before building source and dpkg could skip adding an empty diff.gz to
the end of the dsc in such a case. For many projects you would then
end up with:

Files:
 xxxx yyy foobar.orig.tar.gz
 xxxx yyy debian.svn.tar.gz

(or whatever VCS is used).

MfG
        Goswin