Git Download/Bootstrap Suggestion

I may be missing something, but I would like to request that http://git-scm.com/download provide a link to a tarball of the actual git clone of the current repository with the repo parked on the latest stable. What I mean is that for most of my systems I build git off of source but I like to be able to just git pull when I want to update them. Currently what I have to do is
- download the source tarball (or the rpm)
- make it
- install it
- use that git clone the real repo
- checkout the newest tag
- make configure
- configure
- make
- make install

It'd be a lot cooler if I could just wget a full get repo on the latest tag :)

Just a request, Thanks
-Mike

I had a same question :) what I want is to distribute a git version across some team. I maintain a clone and keep the latest tag checkedout. When ever there is a new release (tag), I switch to master branch and pull. Than I checkout the new tag and compile. Is there any simple way to do this w/o any downtime?. There should be .... I just miss some extra knowledge on git. Thanks in advance for suggestions

Dilip

Heya,

Nah, you don't need to do all that ;).

You mean like, this?

http://repo.or.cz/w/git.git?a=snapshot;h=master;sf=tgz

Cheers,

Sverre Rabbelier

Sverre Rabbelier venit, vidit, dixit 28.03.2009 00:21:

No, I think he meant repo, not work tree.

Michael

Heya,

Why would he need the repo to bootstrap?

Cheers,

Sverre Rabbelier

So he can compile git from a git repo, and not have to download it (again) after compiling from a work tree. Saving a step, and re-compiling a bunch of files when he upgrades.

I'm a bit unclear why you would compile/install the second time - if it's the latest tag, it should be the same as you got from the archive on the website, the second step should just be re-installing the exact same Git. Why not just build it from source the first time and then pull down the full source for the subsequent times - you're losing seconds total in the process. Unless you're doing this all the time, in which case it seems like it makes more sense to just keep one repo, build a package of some sort (rpm, deb, etc) and distribute that to all the computers you're using.

I mean, if you really, really want it then you can :

a) clone the website source : git://github.com/schacon/gitscm
b) write the script that would do it on each release (scripts/ dir)
c) test it
d) write some code that would dynamically link that in the downloads page at the bottom

If that works then I'll probably pull it in for you.

Scott