From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1161201AbcFCUrm (ORCPT <rfc822;w@1wt.eu>);
	Fri, 3 Jun 2016 16:47:42 -0400
Received: from tex.lwn.net ([70.33.254.29]:52319 "EHLO vena.lwn.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1161043AbcFCUrf (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 3 Jun 2016 16:47:35 -0400
Date: Fri, 3 Jun 2016 14:47:32 -0600
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
        Daniel Vetter <daniel.vetter@ffwll.ch>,
        Grant Likely <grant.likely@secretlab.ca>,
        Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
        Dan Allen <dan@opendevise.io>, Russel Winder <russel@winder.org.uk>,
        Keith Packard <keithp@keithp.com>, LKML <linux-kernel@vger.kernel.org>,
        linux-doc@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: rst2pdf (was [PATCH 00/10] Documentation/Sphinx)
Message-ID: <20160603144732.18db8869@lwn.net>
In-Reply-To: <87k2ibfh0x.fsf@intel.com>
References: <cover.1463748027.git.jani.nikula@intel.com>
	<877fec7gfm.fsf@intel.com>
	<CAKMK7uGSwf_jd2Nys=yArmA6voGmbyfTP4UAibswT4rU6yi75Q@mail.gmail.com>
	<36300F5F-C3F3-4A55-9257-788CF9F96CA4@darmarit.de>
	<878tyrbo36.fsf@intel.com>
	<5369C8B8-47F2-4B67-A314-5EB5471ABA00@darmarit.de>
	<87k2ibfh0x.fsf@intel.com>
Organization: LWN.net
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 30 May 2016 23:05:34 +0300
Jani Nikula <jani.nikula@intel.com> wrote:

> > I can't recommend to use rst2pdf (it is less maintained), use default
> > sphinx LaTeX toolchain.  
> 
> I think we'll use whatever works, rst2pdf seemed to work for now, but we
> can change if needed.

I really like the idea of using rst2pdf and keeping the huge latex
dependency out of the mix.  I am a bit concerned, though; I've been able
to crash it in my experiments here.  We may want to have the ability to
support either chain eventually; otherwise, we might just end up picking
up maintenance of rst2pdf at some point so that it works properly for us.

jon