From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Lengthy "xmlto" build step in Cygwin.
Date: Fri, 01 Jul 2016 20:53:00 -0000 [thread overview]
Message-ID: <438a2cac-c7d3-4f5d-d9da-ad98c79b6baf@t-online.de> (raw)
In-Reply-To: <F8B12F74-6D70-413F-BB42-82BCC52976AA@etr-usa.com>
Am 01.07.2016 um 20:36 schrieb Warren Young:
> That means you have the DocBook tools installed but donât have the
> DocBook XSL stylesheets installed, so it has to fetch them over the
> Internet. Those Internet servers are heavily overloaded because of
> all the *other* users with the same system misconfiguration you
> have.
Well, in all fairness it has to be pointed out that this
mis-configuration was set up, or at least not actively prevented, by the
packages involved.
Now the need for these packages _is_ actually mentioned somewhere:
winsup/doc/README:
=======================
ADDITIONAL BUILD REQUIREMENTS FOR DOCUMENTATION
dblatex
docbook-xml45
docbook-xsl
docbook2x-texi
gzip
texinfo
xmlto
=======================
But of these only docbox2x-texi is checked for by
winsup/doc/configure.ac. At least xmlto surely has to be checked for,
too, don't you think? And maybe it would be possible to add a check for
the docbook-xml45 package (or equivalent) here, to at least output a
warning.
Or, to turn this around: shouldn't one of these packages:
xmlto
dblatex
docbook2x
formally require package docbook-xml45 (and possibly all the other
docbook-* packages)?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-07-01 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 18:18 Kaz Kylheku
2016-07-01 18:36 ` Warren Young
2016-07-01 20:53 ` Hans-Bernhard Bröker [this message]
2016-07-01 22:11 ` Warren Young
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=438a2cac-c7d3-4f5d-d9da-ad98c79b6baf@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).