From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: distinguish between HTML vs PDF doc generation packages?
Date: Sat, 10 Jan 2015 06:51:33 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1501100644110.7019@localhost> (raw)
ref manual, section 1.3.2, breaks out the packages required to build
the documentation. first, i think it would be useful to distinguish
between the (much shorter) list of packages needed for HTML versus the
much longer list for PDF, since that second list is typically way
longer and some folks may have no need for it. (from memory, the list
of packages for PDF generation on fedora is ridiculous.)
also, the package list for PDF generation (at least for my fedora
rawhide system) seems out of date. the ref manual claims i need to:
$ sudo yum install make docbook-style-dsssl docbook-style-xsl \
docbook-dtds docbook-utils fop libxslt dblatex xmlto
however, i can build PDF just fine but a quick query shows i don't
have some of the allegedly essential packages:
$ rpm -q make docbook-style-dsssl docbook-style-xsl \
> docbook-dtds docbook-utils fop libxslt dblatex xmlto
make-4.0-3.1.fc22.x86_64
package docbook-style-dsssl is not installed
docbook-style-xsl-1.78.1-3.fc21.noarch
docbook-dtds-1.0-63.fc21.noarch
package docbook-utils is not installed
fop-1.1-8.fc21.noarch
libxslt-1.1.28-8.fc22.x86_64
libxslt-1.1.28-8.fc22.i686
package dblatex is not installed
xmlto-0.0.26-3.fc22.x86_64
$
so it seems i certainly don't need everything suggested by the ref
manual. again, this is on my fedora *rawhide* system so i don't know
if this has changed since the last supported fedora release.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2015-01-10 11:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.11.1501100644110.7019@localhost \
--to=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.