From: Jeff King <peff@peff.net>
To: Drew Northup <drew.northup@maine.edu>
Cc: Andi Kleen <andi@firstfloor.org>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Chris Johnsen <chris_johnsen@pobox.com>
Subject: Re: groff .ft command use in asciidoc
Date: Fri, 19 Nov 2010 15:40:10 -0500 [thread overview]
Message-ID: <20101119204010.GA18342@sigill.intra.peff.net> (raw)
In-Reply-To: <1290198893.13785.68.camel@drew-northup.unet.maine.edu>
On Fri, Nov 19, 2010 at 03:34:53PM -0500, Drew Northup wrote:
> > RHEL5 has asciidoc8, but docbook-xsl 1.69, which means it still needs
> > ASCIIDOC_ROFF enabled. RHEL6 is just out last week. So we are
> > technically breaking at least RHEL5 people (along with anybody with
> > ancient systems) until they tweak their knobs.
>
> Once I imported the DocBook XML XSL 4.5 files into my local cache it
> seemed to make the man pages just fine on my RHEL5 machine even with the
> posted patch applied.
>
> [root@host ~]# rpm -qi asciidoc
> Name : asciidoc Relocations: (not relocatable)
> Version : 8.6.3 Vendor: Dag Apt Repository, http://dag.wieers.com/apt/
> Release : 1.el5.rf Build Date: Thu 18 Nov 2010 08:35:22 AM EST
> ...
> [root@host ~]# rpm -qi docbook-utils
> Name : docbook-utils Relocations: (not relocatable)
> Version : 0.6.14 Vendor: Red Hat, Inc.
> Release : 5.1 Build Date: Wed 12 Jul 2006 03:55:00 AM EDT
>
> I didn't inspect each and every one for errors, but I didn't see any
> problems in the ones I did look at.
I think the updated XSL files are what's making it work. The stock
docbook xsl files are:
$ yum list | grep docbook-style-xsl
docbook-style-xsl.noarch 1.69.1-5.1 rhel-x86_64-server-5
and I don't know that we can assume anyone has updated them. However, I
don't actually build git on my RHEL machines, so I could might be wrong.
All that being said, I am willing to accept RHEL5 as collateral damage
if the new defaults Just Work for the majority of other platforms.
-Peff
next prev parent reply other threads:[~2010-11-19 20:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 9:52 groff .ft command use in asciidoc Andi Kleen
2010-11-17 10:15 ` Jonathan Nieder
2010-11-17 11:52 ` Andi Kleen
2010-11-17 14:38 ` Jeff King
2010-11-17 15:48 ` Andi Kleen
2010-11-19 17:54 ` Jeff King
2010-11-19 18:22 ` Jonathan Nieder
2010-11-19 18:37 ` Jeff King
2010-11-19 20:34 ` Drew Northup
2010-11-19 20:40 ` Jeff King [this message]
2010-11-19 20:53 ` Drew Northup
2010-11-19 22:58 ` Junio C Hamano
2010-11-20 1:48 ` Todd Zullinger
2010-11-18 17:47 ` Alejandro Riveira Fernández
2010-11-18 21:11 ` Drew Northup
2010-11-18 23:15 ` Alejandro Riveira Fernández
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=20101119204010.GA18342@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andi@firstfloor.org \
--cc=chris_johnsen@pobox.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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).