git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: Jack Moore <jhmoore719@verizon.net>
Cc: git@vger.kernel.org
Subject: Re: Building documentation on an isolated network
Date: Sat, 08 May 2010 09:02:18 -0400	[thread overview]
Message-ID: <4BE560DA.2010809@artsci.utoronto.ca> (raw)
In-Reply-To: <393FB43C-317F-4CCB-980F-F56D1126C50F@verizon.net>

On 05/08/2010 04:24 AM, Jack Moore wrote:

> I'm trying to setup a git repository on an isolated (not connected to the internet) network.
 > The repository is to be accessed by several developers on their own 
workstations (all running RHEL 5).
 > I have got git to build and install the executable with no problem, 
but when I try to build the
 > documentation is runs into problems with ASCIIDOC.  I found an 
ASCIIDOC rpm for version 8.x.
 > I think ASCIIDOC is looking for some standard DTDs.  Does anyone have
 > suggestions?

Once you get asciidoc, you should have everything else you need in the 
stock RHEL distribution to build locally.  This would include things like:

xmlto
sgml-common
xml-common
docbook-dtds
docbook-style-xsl

and dependencies for those.  (There might be an important item or two 
missing from that list.  It's from memory.)  Asciidoc is available from 
the EPEL repo if the one you found doesn't work for some reason.

The other suggestion of building just the quick docs is good too unless 
you really want/need them.

HTH.
-Ben

      parent reply	other threads:[~2010-05-08 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-08  8:24 Building documentation on an isolated network Jack Moore
2010-05-08  9:23 ` Tomas Carnecky
2010-05-08 13:02 ` Ben Walton [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=4BE560DA.2010809@artsci.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=git@vger.kernel.org \
    --cc=jhmoore719@verizon.net \
    /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).