Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 24B08431FBC for ; Sun, 4 Jan 2015 01:46:40 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2WATiNLMumIg for ; Sun, 4 Jan 2015 01:46:37 -0800 (PST) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id EB250431FB6 for ; Sun, 4 Jan 2015 01:46:36 -0800 (PST) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1Y7hlc-0005f5-GD; Sun, 04 Jan 2015 05:46:36 -0400 Received: (nullmailer pid 9384 invoked by uid 1000); Sun, 04 Jan 2015 09:46:31 -0000 From: David Bremner To: "notmuch@notmuchmail.org" Subject: who finds support for rst2man in the notmuch build process useful? User-Agent: Notmuch/0.19+10~g215de26 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Sun, 04 Jan 2015 10:46:29 +0100 Message-ID: <87k312x4i2.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2015 09:46:40 -0000 --=-=-= Content-Type: text/plain Recently in discussion of at id:1420300167-5060-1-git-send-email-david@tethera.net it was proposed we could just eliminate support for non-sphinx based methods of building the docs. This would require sphinx >= 1.0 and python-docutils 0.6 to build the docs. The win for us would be to eliminate some custom python scripting in the build process to fake some small part of sphinx functionality; it would also allow us to use more features of sphinx in the .rst source. Version 1.0 of sphinx is from 2010, and is present e.g. in Debian stable. We are having a bit of dependency creep here. One option would be to generate seperate tarballs of the pre-formatted man pages during the release process; this _should_ be a matter of running "tar" on the build tree. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQGcBAEBCAAGBQJUqQv1AAoJEPIClx2kp54sWrIL+wbZnTI+NzvM7IZbEq91D/7A fcj7I+dwM7NWGB3fSGCsRrI9HJqXkJFEpv0pPuLZC0QujbyY118l68tj4J7YMj8V vCIp3J7Vxu9Rybzzl3uEg3NgYGhPE0yFknYD1nGrxe4ZkRsEnmTKu4yEP2AclA4o waKBBby3WMjULnCdFNIcl9X35wvJg2dedlRW5uSXDlg/zyXtOgez/59p2QjUz0Uu zIULWZTXNCgGpQWGWTokJ9Hs2UJsZy0dNojSn9jWjlrrv1pPKOj5tn6N6v5fZiqK XlmARMaN71a0Tz3kTsjoSURmxygsd3FPf0rkW79TI7wRazTK3exucD6Qzv8Npyqb H09x6dH+RNvyJ6Mtu+p93mmX7bUe29DfYhMmFbIOFivPelYuCyflLfVnyT6emCVr /2oA6YAlYvQChwToRvubwCNtt+B3xXi83y3KiYy4TF4AKc3DvD3SHkFmqZBHVGMg wXl5VwJhFFvnc2MHlG+cAiCrGerZVG+dN9a296lawg== =0TZB -----END PGP SIGNATURE----- --=-=-=--