Closed GoogleCodeExporter closed 8 years ago
Hi. You can download a zip from github, for latest ver or for any tag version.
https://github.com/stuntrally/stuntrally/tags
and also for tracks
https://github.com/stuntrally/tracks/tags
Just put tracks into data/tracks/
Original comment by Cry...@gmail.com
on 25 May 2012 at 8:25
Thanks for the quick reply. We are aware of that it is possible to manually
pull all sort of wonderful things from git. I did read the documentation on
your site, and indeed it's quite easy to manually pull an update from git.
The problem comes in when one wants an unattended computer to realize when a
new version is released, and pull the update.
With literally thousands of packages and only a handful of maintainers,
automation is the only way of keeping our entire distrobution up to date.
If a package is in a tarball in a directory that was not there the last time
the directory was checked with curl, and the name of the tarball matches the
package string, one can deduce the version without too much difficulty, pull
the tarball and make patch files all without human intervention.
I do not know of a way to do something similar in git, and git repositories add
quite a bit of version information which is not needed for compilation and
installation.
When you release a new version of StuntRally, posting the tarball in the
directory can be seen as a type of release announcement, and it should be
trivial do with git.
If this is too much trouble on your side, I do understand fully.
Unfortunately we can't support git as a way of distributing sources for a
distribution. This would unfortunately mean that we drop StuntRally from our
list of packages, which in turn loses you some talented bug-hunters that will
go get their racing fix somewhere else.
Kind regards,
-Evert Vorster-
Original comment by evors...@gmail.com
on 25 May 2012 at 9:02
Again, the tarball is available at github, without the need for git. E.g.
latest release 1.6's tar.gz:
https://github.com/stuntrally/stuntrally/tarball/1.6
Github makes this automatically for us, so we'd rather not duplicate work.
Whenever there is a new directory on sf.net, there should be a new tarball in
github so just direct the actual download to the new url. There is even no
version deduction needed, because the directory name will be the version, which
is also used in the github tarball url. Is there a flaw in my logic?
--
If you supported git, a new version would be very easy to find out (assumes the
repo cloned):
$ git pull # Updates the sources
$ LATEST=`git tag | tail -1` # Latest release is now in LATEST, e.g. "1.6"
$ wget https://github.com/stuntrally/stuntrally/tarball/$LATEST # Download
the tarball, so no git stuff in the archive
Original comment by tapiovie...@gmail.com
on 26 May 2012 at 6:47
Original comment by Cry...@gmail.com
on 26 May 2012 at 2:40
so i'm closing.
Original comment by Cry...@gmail.com
on 31 May 2012 at 7:17
Original issue reported on code.google.com by
evors...@gmail.com
on 25 May 2012 at 7:29