From: Sebastian Pipping <sping@gentoo.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Rustom Mody <rustompmody@gmail.com>,
git@vger.kernel.org, "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: requesting info page (and pdf) doc releases
Date: Fri, 23 Oct 2009 21:22:12 +0200 [thread overview]
Message-ID: <4AE20264.2060207@gentoo.org> (raw)
In-Reply-To: <7vtyxqaqg5.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Rustom Mody <rustompmody@gmail.com> writes:
>
>> On Fri, Oct 23, 2009 at 2:11 AM, Sebastian Pipping <sping@gentoo.org> wrote:
>>> would be nice to get info pages (and pdf) doc releases in addition to
>>> html and man pages. i imagine such a change to the release machine
>>> should not be too hard to integrate. we could use it in gentoo.
>> +1
>> Why only gentoo? I would use it on ubuntu or windows as well
>
> As I understand it, Gentoo is supposed to build everything from the source
> anyway, you would not want to use pregenerated info nor pdf, no? You
> shouldn't be using pregenerated html nor man for that matter...
With "compiling" documentation things are a bit different.
Simplified, in contrast to source code compiling documentation leads to
the same results on all machines while sources produces lots of
different results depending on the configuration of the machine ("use
flags", compile flags, versions of linked libraries, ..) which differ
heavily from one machine to another.
Generating documentation downstream means more dependencies for us
without any advantages that I would be aware of. In case of dblatex the
dependencies get quite extreme actually :-) So we thought why not just
ask for it if you provide similar things already.
> FWIW, you can already say "make info" and "make pdf" yourselves if you
> have necessary toolchains installed. Integration is not an issue.
We use make info at the moment. (On a sidenote I hope you get it
working with the latest asciidoc again. See my earlier mail on this list.)
> Neither my primary development box (Debian, which I would test before
> pushing things out) nor the machine at k.org I use for the final sanity
> check (FC11, on which the documents are automatically generated) has
> dblatex nor docbook2x installed. I am not particularly enthused about
> installing a lot of dependencies for these packages on my machine. I do
> not want to bother k.org admins who are already overloaded to install
> these on their machines either.
I see, thanks for your explanation.
Sebastian
prev parent reply other threads:[~2009-10-23 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 20:41 requesting info page (and pdf) doc releases Sebastian Pipping
2009-10-22 22:13 ` Rustom Mody
2009-10-23 8:39 ` Michael J Gruber
2009-10-23 18:57 ` Junio C Hamano
2009-10-23 19:22 ` Sebastian Pipping [this message]
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=4AE20264.2060207@gentoo.org \
--to=sping@gentoo.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robbat2@gentoo.org \
--cc=rustompmody@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).