Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] classes/sanity: remove texi2html from required host utilities
Date: Mon, 20 Aug 2012 10:50:26 +0100	[thread overview]
Message-ID: <5299780.5uPXUKxR1v@helios> (raw)
In-Reply-To: <1345452500.24626.83.camel@x121e.pbcl.net>

On Monday 20 August 2012 09:48:20 Phil Blundell wrote:
> On Mon, 2012-08-20 at 09:47 +0100, Paul Eggleton wrote:
> > texi2html is not actually required to build world of OE-Core anymore,
> > so we don't need to mandate it. The only difference without it (verified
> > with buildhistory) is that groff doesn't produce HTML documentation; the
> > rest of its docs are still produced and packaged and no other packages
> > are affected.
> 
> Can we fix groff to make it not even try to use texi2html even if it's
> installed?  It seems a bit undesirable for the amount of documentation
> you get to vary depending on the host environment.

Actually, upon closer inspection, texi2html has nothing to do with this. The 
host needs to have pnmcut, pnmcrop, pnmtopng, psselect, pnmtops and gs 
installed or neither the HTML nor PDF backends for groff will be enabled.

This leaves us with two alternatives:

1) Make groff depend on ghostscript, and that would at least enable the PDF 
backend, but for HTML it still leaves netpbm (for pnm*) and psutils (for 
psselect), neither of which we have in OE-Core.

2) Alternatively I can add --without-gs to the groff configure options which 
will always disable both backends.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-08-20 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20  8:47 [PATCH] classes/sanity: remove texi2html from required host utilities Paul Eggleton
2012-08-20  8:48 ` Phil Blundell
2012-08-20  9:50   ` Paul Eggleton [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=5299780.5uPXUKxR1v@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox