Full source tarball (packed .org.tar.gz file) in SVN, instead of plain FTP/HTTP? Why? Any exceptions?

Eddy Petrișor

No. See my numerous explanations and the alternative location. No exceptions.

Gonéri Le Bouder

Tarballs are not designed to by versioned. This is just useless. In general game tarballs a much bigger than for others type of software (just to by more than 100MB) and we must be kind to svn.d.n and http download is much faster.

Linas Žvirblis

Same as ↑

Reinhard Tartler

I don't see much problems with having upstream tarballs in svn. It is right that tarballs are not meant to be versioned, but here, svn is used as a versioned directory. The same happens when using patch systems. Interestingly, the same ppl advocating using patch systems like quilt or dpatch are strongly against having upstream tarballs in svn.

Alexander Schmehl

Linas already explained, why it doesn't make sense. But I definetly think, we should but all our tar-balls somewhere central (e.g. our web-site on alioth.)

Jon Dowland

The tarballs need to be stored somewhere. If they're in SVN, but not in the normal paths (so won't be checked out accidentally), then we can use the same tools to obtain the tarballs as the rest of the source. It saves us remembering another HTTP path.

Sam Hocevar

Many of my upstreams are dead, I need a place to store tarballs. They don’t change often, and don’t take that much space.

Andres Mejia

No. Like I said in the previous section. Some games are huge and all changes can be done in the debian directory. A central location to store tarballs is ok.