From: Junio C Hamano <gitster@pobox.com>
To: "Bert Wesarg" <bert.wesarg@googlemail.com>
Cc: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
guilt@lists.josefsipek.net, "Brandon Philips" <brandon@ifup.org>
Subject: Re: [ANNOUNCE] Guilt v0.31
Date: Mon, 08 Sep 2008 12:17:25 -0700 [thread overview]
Message-ID: <7vmyiifnwa.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <36ca99e90809081150v4ad6e7a0n72b5cca39e02b1bc@mail.gmail.com> (Bert Wesarg's message of "Mon, 8 Sep 2008 20:50:03 +0200")
"Bert Wesarg" <bert.wesarg@googlemail.com> writes:
> I must admit, that I don't like these extra tarballs with docs. I
> always expect, that the manpages are nicely installed if I type 'make
> install' (or at least with a install-doc target). But I need to
> download this extra package, and extract it to the right place, there
> is no Makefile whatsoever. In case of git its really annoying, because
> the help mechanism is relying on the manpages (i.e. git help <cmd> or
> git <cmd> --help, but you know this).
There is no need to feel "it[']s really annoying", as install-doc from the
tarball distribution works out of the box.
I used 1.6.0.1 in the demonstration below, but this is nothing new in that
version but has been like this for quite some time (it is how sample RPMs
binary packages are built, so the procedure ought to work):
$ ls -1 /usr/bin/git ;# to show there is no other "git" on this box
ls: /usr/bin/git: No such file or directory
$ mkdir /var/tmp/16
$ cd /var/tmp/16
$ wget http://www.kernel.org/pub/software/scm/git/git-1.6.0.1.tar.gz
$ tar xf git-1.6.0.1.tar.gz
$ cd git-1.6.0.1
$ make prefix=/var/tmp/16test install install-doc
$ PATH=/var/tmp/16test/bin:/usr/bin:/bin
$ export PATH
$ unset MANPATH
$ git help cat-file | cat -s | tail -n 8
Reformatting git-cat-file(1), please wait...
DOCUMENTATION
Documentation by David Greaves, Junio C Hamano and the git-list
<git@vger.kernel.org>.
GIT
Part of the git(1) suite
Git 1.6.0.1 09/08/2008 GIT-CAT-FILE(1)
The extra tarballs for documentation are also given as courtesy because
they are supposed to be platform independent and some people do not want
to generate them themselves (even though they could).
Either be thankful for the availability of tarballs, or ignore them and
generate them yourself --- it's your choice.
next prev parent reply other threads:[~2008-09-08 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 13:52 [ANNOUNCE] Guilt v0.31 Josef 'Jeff' Sipek
2008-09-08 15:39 ` Michael J Gruber
2008-09-08 15:45 ` Josef 'Jeff' Sipek
2008-09-08 15:58 ` Josef 'Jeff' Sipek
2008-09-08 18:33 ` Bert Wesarg
2008-09-08 18:43 ` Josef 'Jeff' Sipek
2008-09-08 18:50 ` Bert Wesarg
2008-09-08 19:17 ` Junio C Hamano [this message]
2008-09-09 10:10 ` Michael J Gruber
2008-09-09 13:02 ` Michael J Gruber
2008-09-09 15:13 ` Junio C Hamano
2008-09-09 15:40 ` Michael J Gruber
2008-09-09 16:02 ` Junio C Hamano
2008-09-09 16:29 ` Michael J Gruber
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=7vmyiifnwa.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bert.wesarg@googlemail.com \
--cc=brandon@ifup.org \
--cc=git@vger.kernel.org \
--cc=guilt@lists.josefsipek.net \
--cc=jeffpc@josefsipek.net \
--cc=linux-kernel@vger.kernel.org \
/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).