mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: The downside of math::
Date: Fri, 21 Oct 2016 15:38:06 -0600	[thread overview]
Message-ID: <20161021153806.5c9b5d7b@lwn.net> (raw)
In-Reply-To: <877f93qdd2.fsf@intel.com>

On Thu, 20 Oct 2016 17:55:21 +0300
Jani Nikula <jani.nikula@linux.intel.com> wrote:

> I wonder if we could cook up a nice way to make the math:: usage
> conditional on actually being able to render it.

I think that's the ideal solution.

I got the docs build working again on my Fedora machine, but it threw me
back into this loop for several iterations:

	while (htmldocs build fails)
		see which goddam LaTex file is missing now
		dig around to find which Fedora package provides it
		dnf install YA-texlive-package

This is just the kind of thing that I don't want to impose on anybody
wanting to build the docs; if we get back to a place where almost nobody
can do it again, we'll not have improved much.

LaTeX is a necessary evil for PDF output, it seems, but I really think
that, one way or another, we need to be able to build the other formats
without it.

Thanks,

jon

  parent reply	other threads:[~2016-10-21 21:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 23:02 Jonathan Corbet
2016-10-20  0:26 ` Mauro Carvalho Chehab
2016-10-20  0:48   ` Mauro Carvalho Chehab
2016-10-20 14:55   ` Jani Nikula
2016-10-20 15:15     ` Markus Heiser
2016-10-21 21:38     ` Jonathan Corbet [this message]
2016-10-23 10:58       ` Markus Heiser
2016-10-24  7:52         ` Johannes Berg
2016-10-24  8:22           ` Jani Nikula
2016-10-24  8:26             ` Johannes Berg
2016-10-24  9:06               ` Jani Nikula

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=20161021153806.5c9b5d7b@lwn.net \
    --to=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@s-opensource.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

all inboxes | Powered by JetHome®