X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=PMIreCj5aXXw4eg6BUkXdpD2Lf0t
	IqQBz/r9dbKOWpCGDzi1aADJhfG3ASxjs0kpBwsKxD3xeNz4j7e3QZ4JZvP7mssX
	Az8eh4YdD/67F4EP05q1td3F4xmtW6URZw5AzdQezxzX9Qf/QH/0xcEjqsV4UYGG
	DXhfjCQULDFfvBg=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=du2TKJ6vX21jbI10VbO/4ziFZsQ=; b=l3
	yE/Ahp4OKw3YE6v/zkt8I+ZyGaZtcv6gCwCjeoFpzimlQvhISrSixvi1QisZjrS5
	dAZ1Hnkj++M66BO1VFM7C4X6bMt7+jAajzvpDYEIgXbKhZGTbE2GjzOAmc/0t8Mu
	8FDiCN8XxOTf3MLCMNYeUEQuohobMX78MhROBeQew=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=curve, brker, hans-bernhard, hansbernhard
X-HELO:	etr-usa.com
Mime-Version:	1.0 (Mac OS X Mail 9.3 \(3124\))
Subject:	Re: Lengthy "xmlto" build step in Cygwin.
From:	Warren Young <wyml AT etr-usa DOT com>
In-Reply-To:	<438a2cac-c7d3-4f5d-d9da-ad98c79b6baf@t-online.de>
Date:	Fri, 1 Jul 2016 16:11:20 -0600
Message-Id:	<B49BF5CE-2C68-483C-89C1-9EDEC58A4C1A@etr-usa.com>
References:	<bfbac5abef5b3937edd1f9814c5f4bc8 AT mail DOT kylheku DOT com> <F8B12F74-6D70-413F-BB42-82BCC52976AA AT etr-usa DOT com> <438a2cac-c7d3-4f5d-d9da-ad98c79b6baf AT t-online DOT de>
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u61MBh6R010089

On Jul 1, 2016, at 2:52 PM, Hans-Bernhard Bröker wrote:
> 
> 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
> 
> only docbox2x-texi is checked for by winsup/doc/configure.ac.

You’re in a fine position to fix that, then. :)

> At least xmlto surely has to be checked for, too, don't you think?

That and xsltproc, at least.

> And maybe it would be possible to add a check for the docbook-xml45 package

The trick is finding that out portably.

You can’t check for version 4.5 stylesheets specifically, because someday the docs may move to DocBook 5.

You also can’t use Cygwin-specific methods to check for this because the docs are also built on non-Cygwin systems.  The official builds of everything under winsup are in fact cross-compiled on a Fedora box rather than built under Cygwin.

Finally, the stylesheets may be in different locations on different machines.

Probably the most portable method is something like

   if ! grep -q file://.*docbook /etc/xml/catalog
   then
       AC_MSG_ERROR([the DocBook stylesheets are not installed])
   fi

Consider that pseudocode.  (Untested, written off the top of my head.)

> Or, to turn this around: shouldn't one of these packages:
> 
> 	xmlto
> 	dblatex
> 	docbook2x
> 
> formally require package docbook-xml45

Certainly not xmlto or xsltproc, as they’re both used for more than DocBook.

dblatex could, I suppose, but you’ll find that Fedora doesn’t tie those two together, either:

  http://koji.fedoraproject.org/koji/rpminfo?rpmID=7275706

That’s probably because dblatex will consume either XSL or SGML stylesheets, and they don’t want to depend on both.  Plus, as you’ve found, the network fetch option does work; it’s just sllllooooow.

Even if you fix that, there's more than just dblatex for rendering DocBook to PDF, so you’d have to chase all those avenues, too.  For instance, there’s FOP, which isn’t DocBook specific, so making docbook-xsl a dependency of it would be wrong, so you’re left hangnig.

docbook2x is perhaps a better candidate, though I don’t actually see a reason it’s the only possible build option.  I suspect you could do everything it does in pure XSLT, obviating the need for it.  So, you’d still need to call out the need for docbook-xsl in the build instructions.

Bottom line, you just have to know you need these things, if you’re going to work with DocBook.  It’s just part of the learning curve.
--
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

- Raw text -