Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage
- To: Russ Allbery <rra@debian.org>
- Cc: debian-devel@lists.debian.org
- Subject: Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Date: Wed, 20 Jan 2010 16:49:26 +0100
- Message-id: <[🔎] 87d414ojy1.fsf@frosties.localdomain>
- In-reply-to: <87r5qdwrm8.fsf@windlord.stanford.edu> (Russ Allbery's message of "Tue, 29 Dec 2009 10:40:47 -0800")
- References: <20091228001446.GC13111@gamma.logic.tuwien.ac.at> <20091228002517.GA4528@teal.hq.k1024.org> <20091228003843.GD13111@gamma.logic.tuwien.ac.at> <20091228080929.GA26700@teal.hq.k1024.org> <87iqbqc0b2.fsf@windlord.stanford.edu> <hhbk29$b6m$1@ger.gmane.org> <hhc76c$db0$1@ger.gmane.org> <87637qth99.fsf@windlord.stanford.edu> <1262111683.28016.1.camel@pcfelipe.sateler.com> <87r5qdwrm8.fsf@windlord.stanford.edu>
Russ Allbery <rra@debian.org> writes:
> Felipe Sateler <fsateler@gmail.com> writes:
>> On Mon, 2009-12-28 at 22:40 -0800, Russ Allbery wrote:
>
>>> I think the way forward for Git-maintained packages is the 3.0 (git)
>>> format, but changed to ship a bundle. That way, relevant branches and
>>> history can be included, and Git is fairly space-efficient so the
>>> additional cost of doing so isn't that bad.
>
>> Why go through the hassle of creating a git format when patching dak to
>> import a VCS-signed tag (which may be mor difficult, I agree) is much
>> more efficient?
>
> That doesn't solve the same problem as near as I can tell. That's a
> replacement for the upload process, but once dak has imported the signed
> tag and has a copy of the repository, now what? How is that data
> represented? How is it distributed to Debian systems that want to
> download the source package? I think you end up reinventing 3.0 (git) as
> a format for redistributing the thing that dak has pulled as a signed tag.
apt-get source foo
APT: Oh, foo is a git source
git clone http://ftp.de.debian.org/debian/git/main/f/foo
MfG
Goswin
Reply to: