Re: [PATCH] proposed v3 source format using .git.tar.gz
On Sun, Oct 07, 2007 at 10:18:17PM +1000, Anthony Towns wrote:
> On Sun, Oct 07, 2007 at 08:45:08AM +0000, Colin Watson wrote:
> > I'm quite attached to being able to peek inside source packages
> > quickly by sshing over to the local mirror I keep at home which
> > grabs everything overnight so that I don't have to wait for it to
> > download; particularly so for large source packages.
>
> How is that better than running "apt-get source" against your local
> mirror, though?
Faster for some cases involving huge packages where I don't want to
transfer the whole thing over wireless. Doesn't require complex apt
configuration to point to the right package if what I want isn't the
current version in the release I'm running. Etc.
> Alternatively, is it really a problem to have your local mirror
> autogenerate v1 source packages in the same way v1source.qa.d.o presumably
> would?
I suppose that would be possible (if the code were properly packaged,
integrated into debmirror, etc.), though it sounds like a big chunk of
resources on my rather underpowered mirror server. (Yes, that's my
problem, but I'm sure I'm not the only one.) I also can't see general
mirrors like mirrorservice.org doing this kind of highly distro-specific
thing, so we'd still lose handy "look at a single file within this
package on the web" tools unless we reimplemented them on debian.org
systems. Those sorts of things are very useful for big source packages.
> (I have a strong adverse reaction to duplicated information, so shipping
> the working tree in .git format and .orig.tar.gz format irks me,
> particularly if it's required)
I do understand this reaction though ...
> > Oh, I was referring more to the buildd base system and archive
> > maintenance code too; dak needs to be updated in order to accept format
> > 3.0 source packages, for instance.
>
> Well, you'd need an entirely new .dsc to use a v3 source package with
> an un-updated dak (or launchpad or whatever), that didn't contain the
> .git.tar.gz (or whatever) elements at all, so I don't personally see a
> lot of difference between just generating a new .dsc and generating a
> new .dsc and .tar.gz.
True; I was thinking that a quick hack to permit v3 while still
basically just unpacking .tar.gz and .diff.gz would be easier than full
support for a derivative distribution that wasn't paying a whole lot of
attention, but maybe it doesn't make that much difference.
--
Colin Watson [cjwatson@debian.org]
Reply to: