Re: Let dak commit all source packages to Git
On 11/07/2012 05:21 PM, Ansgar Burchardt wrote:
> Thomas Koch <firstname.lastname@example.org> writes:
>> For every debian source package that enters the archive, dak should commit the
>> source code to a public readable Git repository and put a signed tag on it.
I would use such service!
> I do not think that is a good idea:
> You would end with two repositories for packages maintained in Git.
By reading debian/control and the VCS fields, we could do it *only*
for packages not maintained through Git, if you want to save space
on that. Though I think both repositories would be good, because
the maintainer's Git would contain a lot more individual commits
which wont be in the central package Git repository. They would
serve different purposes.
> It has the same problems with non-free files in the history as 3.0
> (git). Actually worse as the maintainer cannot remove parts of the
> history in a later upload.
We have the same trouble with snapshot.debian.org, and Alioth, no?
> It duplicates large amounts of data already available elsewhere. And all
> repositories would have to live on ftp-master so that dak could commit
> to them.
> I would also expect Git repositories for packages including binary data
> like images, videos or audio to get very large.
Yes, it's going to be huge! But if it is doable, I think it would be really
a very convenient service. When snapshot.d.o was created, I heard
about 12 TB of data. How big is it now?
> I am also not sure why dak should do this. It can be done somewhere
> else, just like snapshot.d.o.
I agree with you. Any Debian mirror could be used, and commits could
happen when new packages are pushed to the mirror.