git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Alex Riesen <raa.lkml@gmail.com>,
	Thiago Farina <tfransosi@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Add more instructions about how to install git.
Date: Tue, 08 Sep 2009 09:56:49 +0200	[thread overview]
Message-ID: <4AA60E41.5050702@drmicha.warpmail.net> (raw)
In-Reply-To: <vpqhbvekldk.fsf@bauges.imag.fr>

Matthieu Moy venit, vidit, dixit 08.09.2009 08:20:
> Alex Riesen <raa.lkml@gmail.com> writes:
> 
>> On Tue, Sep 8, 2009 at 07:11, Thiago Farina<tfransosi@gmail.com> wrote:
>>> Signed-off-by: Thiago Farina <tfransosi@gmail.com>
>>> ---
>>>  INSTALL |    9 +++++++++
>>>  1 files changed, 9 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/INSTALL b/INSTALL
>>> index ae7f750..67abfc7 100644
>>> --- a/INSTALL
>>> +++ b/INSTALL
>>> @@ -1,6 +1,15 @@
>>>
>>>                Git installation
>>>
>>> +To install git follow these 4 steps inside your git directory:
>>> +$ autoconf      # Generates the configure file from configure.ac
>>> +$ ./configure   # Configures everything needed to build git
>>> +$ make all      # Compiles git based in the Makefile
>>> +$ make install  # Installs git in your own ~/bin directory
> 
> Your commit message doesn't say what's wrong with
> 
> | Alternatively you can use autoconf generated ./configure script to
> | set up install paths (via config.mak.autogen), so you can write
> | instead
> | 
> |         $ make configure ;# as yourself
> |         $ ./configure --prefix=/usr ;# as yourself
> |         $ make all doc ;# as yourself
> |         # make install install-doc install-html;# as root
> 
> which is already in INSTALL a few lines after what your patch adds.

... especially since that really is a second class alternative these
days, with using the shipped Makefile being the preferred way - just as
the current documentation states.

> 
>>> +If you don't have autoconf installed, you can do this by:
>>> +$ sudo apt-get install autoconf
>>
>> ... if you're on a Debian-derived system. 
> 
> and if you have sudo configured.
> 
> BTW, apt-get is anyway somehow deprecaded, you should
> s/apt-get/aptitude/.
> 

  reply	other threads:[~2009-09-08  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08  5:11 [PATCH] Add more instructions about how to install git Thiago Farina
2009-09-08  5:44 ` Alex Riesen
2009-09-08  6:20   ` Matthieu Moy
2009-09-08  7:56     ` Michael J Gruber [this message]
2009-09-08 14:24     ` Thiago Farina
2009-09-08 14:37       ` Erik Faye-Lund
2009-09-08 14:38       ` Johannes Sixt
2009-09-08 14:52         ` Thiago Farina
2009-09-08 14:56           ` Mikael Magnusson
2009-09-08 15:19           ` Brian Gernhardt
2009-09-08 19:41           ` Matthieu Moy

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AA60E41.5050702@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    --cc=tfransosi@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).