git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <chriscool@tuxfamily.org>, git@vger.kernel.org
Subject: Re: [BUG] Failed to make install-info
Date: Fri, 14 Dec 2007 08:38:08 -0600	[thread overview]
Message-ID: <E1J3Bg0-0004Ut-Ii@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 13 Dec 2007 22:03:55 PST." <7vejdpvmlw.fsf@gitster.siamese.dyndns.org>

So, like, the other day Junio C Hamano mumbled:
> 
> I personally feel that calling "install-info" is a bit too distro-ish
> and should not be done in our Makefile vanilla build-and-install
> procedure.

Hmmm...  That's an interesting take on things
given the top of the INSTALL file:

		    Git installation

    Normally you can just do "make" followed by "make install", and that
    will install the git programs in your own ~/bin/ directory.  If you want
    to do a global install, you can do

	    $ make prefix=/usr all doc info ;# as yourself
	    # make prefix=/usr install install-doc install-info ;# as root

Granted, it's the first time I've actually tried
to install the docs on this (debian) machine too.
I've normally just read them straight out of the
doc directory. :-)

But I will have to agree with you on the problems
surrounding the One Install to Rule Them All (and
in the darkness bind9 them).

jdl

  reply	other threads:[~2007-12-14 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 15:38 [BUG] Failed to make install-info Jon Loeliger
2007-12-14  5:35 ` Christian Couder
2007-12-14  6:03   ` Junio C Hamano
2007-12-14 14:38     ` Jon Loeliger [this message]
2007-12-14 17:45       ` Junio C Hamano

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=E1J3Bg0-0004Ut-Ii@jdl.com \
    --to=jdl@jdl.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).