From: Scott Chacon <schacon@gmail.com>
To: Jacob Helwig <jacob.helwig@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Mike Gaffney <mr.gaffo@gmail.com>,
git@vger.kernel.org
Subject: Re: Git Download/Bootstrap Suggestion
Date: Sun, 29 Mar 2009 16:29:38 +0100 [thread overview]
Message-ID: <d411cc4a0903290829p7e7ad14aob62e222877956ba5@mail.gmail.com> (raw)
In-Reply-To: <8c9a060903280924h62f4d7aq47819bf3264e6ad6@mail.gmail.com>
On Sat, Mar 28, 2009 at 5:24 PM, Jacob Helwig <jacob.helwig@gmail.com> wrote:
> 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
> On Sat, Mar 28, 2009 at 09:15, Sverre Rabbelier <srabbelier@gmail.com> wrote:
>> Heya,
>>
>> On Sat, Mar 28, 2009 at 17:09, Michael J Gruber
>> <git@drmicha.warpmail.net> wrote:
>>> No, I think he meant repo, not work tree.
>>
>> Why would he need the repo to bootstrap?
>>
>> --
>> Cheers,
>>
>> Sverre Rabbelier
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-03-29 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 17:09 Git Download/Bootstrap Suggestion Mike Gaffney
2009-03-27 23:21 ` Sverre Rabbelier
2009-03-28 16:09 ` Michael J Gruber
2009-03-28 16:15 ` Sverre Rabbelier
2009-03-28 16:24 ` Jacob Helwig
2009-03-29 15:29 ` Scott Chacon [this message]
2009-03-28 7:24 ` Dilip M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d411cc4a0903290829p7e7ad14aob62e222877956ba5@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jacob.helwig@gmail.com \
--cc=mr.gaffo@gmail.com \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).