Re: tarballs - why in SVN?
On 14/08/06, Reinhard Tartler <firstname.lastname@example.org> wrote:
"Eddy Petriÿor" <email@example.com> writes:
> I was wondering, since SVN can't check out just one file, orig
> tarballs do not change for a release and every new upstream release
> will bring a new version, does it make sense in keeping orig tarballs
> in SVN? I would say no and suggest moving all of them in the web
> sapace or the FTP space of the project. This will not force somebody
> wanting to build a package to checkout hundereds of MB just for one
> 500kB file.
> What do you say?
I'd prefer having the full source in svn. At least for the packages
'scorched3d' and 'openal', possibly for 'freealut' as well.
As I don't use svn-buildpackage at all, removing the source from the
SVN makes it painful for me to construct the source package.
Nobody said a thing against sources in svn (yet :-D ), I was
complainaing about the orig tarballs themselves like they are in
I don't see any reason to have the packaged tarballs in SVN and was
suggesting to move all the tarballs under ftp or http space.
"Imagination is more important than knowledge" A.Einstein