From: Mark Rosenstand <mark@borkware.net>
To: git@vger.kernel.org
Subject: Re: Shipping man pages?
Date: Thu, 18 May 2006 11:41:38 +0200 [thread overview]
Message-ID: <1147945298.1320.35.camel@mjollnir> (raw)
In-Reply-To: <7vac9f69la.fsf@assigned-by-dhcp.cox.net>
On Thu, 2006-05-18 at 01:06 -0700, Junio C Hamano wrote:
> Tilman Sauerbeck <tilman@code-monkey.de> writes:
>
> > atm, the git release tarballs don't contain man pages.
>
> I ship *source* tarball.
Which is great for generating binaries and other things that are likely
to be incompatible across systems.
> I also happen to do RPM for people who do not want to build from
> the source (btw, I do that from pure inertia). In addition,
> preformatted manual pages and html docs are available from man
> and html branches of the git.git repository.
>
> If you are building from the source, please build from the
> source. Everything you need is right there.
But asciidoc is a royal PITA to package or install - it doesn't even
provide a Makefile: http://www.methods.co.nz/asciidoc/userguide.html#X38
Additionally it carries the whole docbook dependency chain with it.
> If you don't build from the source, please use whatever binary
> distribution available out there. RPM happens to be available
> from kernel.org. If you are on Debian/Ubuntu/Gentoo/others,
> please ask your distribution packager to include the manpages
> and html docs, if they don't already.
Even the packagers are likely to hate the unneccessary asciidoc
dependency. As a result some of the small distributions that don't have
the manpower to support 1000+ packages choose to ship git without the
man pages, which is a shame, IMO.
> Why does this have to come up so often, and everybody who asks
> for them never supplies the patch to do so?
Because it seems like a political decision rather than a technical one
(it's trivial to add the docs as a prerequisite for the dist target.)
> > Or maybe offer them in a separate tarball?
>
> Things that are buildable from the source do not belong in the
> source tarball. If somebody wants to do this as a patch, I can
> be talked into accepting it, but the build procedure should
> build a separate tarball (or two; one for man and another for
> woman^Whtml).
That would be great! I'd love to submit a patch, but I wouldn't be able
to test it, because I'd need asciidoc.
next prev parent reply other threads:[~2006-05-18 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 7:46 Shipping man pages? Tilman Sauerbeck
2006-05-18 8:06 ` Junio C Hamano
2006-05-18 9:41 ` Mark Rosenstand [this message]
2006-05-18 18:33 ` Junio C Hamano
2006-05-18 18:49 ` Linus Torvalds
2006-05-18 10:57 ` Tilman Sauerbeck
2006-05-18 8:10 ` Fernando J. Pereda
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=1147945298.1320.35.camel@mjollnir \
--to=mark@borkware.net \
--cc=git@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).