tarball link stable?

[GoogleCodeExporter]

Hi,

I hope you can release the project via built-in download function of googlecode 
or switch to github by using tags.

Currently you release lz4 via dropbox, well... I can't say it's bad but somehow 
we're always not easy to track the update.

Thanks.

Original issue reported on code.google.com by Cickumqt on 31 Dec 2013 at 6:34

[GoogleCodeExporter]

I'm not sure to properly understand what is the requirement here.

I've re-enabled the download tab within the project, and put there the same 
tarball as the one linked from the homepage.

My question is : is that what you are looking ?
If yes :
Could you explain in which way it helps you (as compared to linking from 
Homepage) and how you foresee future version changes ?

Original comment by yann.col...@gmail.com on 31 Dec 2013 at 1:29

[GoogleCodeExporter]

In common upstream should releases their projects like:

%{name}-%{version}.tar.gz/.bz2/.zip etc.

You named it lz4-r110.tar.gz, it's fine, we can track it now.

Because google code won't change the URL, but dropbox will so we can track from:

https://lz4.googlecode.com/files/%{name}-r%{version}.tar.gz

Thanks.

Original comment by Cickumqt on 31 Dec 2013 at 5:36

[GoogleCodeExporter]

OK that's clear

Original comment by yann.col...@gmail.com on 2 Jan 2014 at 1:52

• Changed state: Fixed

[GoogleCodeExporter]

Unfortunately, with Google Code killing off its "Download" feature, I'm afraid 
this wasn't a viable long term solution. So now, another solution will have to 
found.

Btw, I've never seen Dropbox change URL so far. What makes you believe it 
happens ?

Original comment by yann.col...@gmail.com on 4 Feb 2014 at 2:30

[GoogleCodeExporter]

Because it looks more "professional"

Plus, good habit.

Welcome to github or bitbucket! You can close this now.

Original comment by Cickumqt on 7 Feb 2014 at 9:02