From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Antoine Amarilli <a3nm@a3nm.net>, notmuch@notmuchmail.org
Subject: Re: Bug: INSTALL should mention python3-sphinx not python-sphinx
Date: Wed, 10 Jan 2018 11:15:20 -0500 [thread overview]
Message-ID: <87wp0p3d2f.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20180110153000.jckdavxrom7ibhy4@zeta>
On Wed 2018-01-10 16:38:18 +0100, Antoine Amarilli wrote:
> In the current master (a727e7d4d398375c4a3ba5020e2ab25b5b874785),
> INSTALL contains:
>
> For Debian and similar:
>
> sudo apt-get install libxapian-dev libgmime-3.0-dev libtalloc-dev zlib1g-dev python-sphinx
>
> However it seems like what is currently used is python3-sphinx, cf
> commit 03f4f75124c6d9882b8306873e8908aac9eee2bb. At least on my system,
> when I have just python-sphinx installed instead of python3-sphinx,
> ./configure says it will not build man pages, whereas it works with
> python3-sphinx.
>
> So I think the line above should be changed.
woops, this sounds correct to me. it would actually have built manpages
if you didn't have python3 installed at all :) but sensible machines do
have python3 these days, so we should be optimizing for those
situations.
> Probably the Fedora line just below needs to be changed too, but I
> don't know how their packaging work (do they have a python3-sphinx
> package or not).
https://developer.fedoraproject.org/tech/languages/python/sphinx.html
suggests that they do have one with the same name.
--dkg
prev parent reply other threads:[~2018-01-10 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 15:38 Bug: INSTALL should mention python3-sphinx not python-sphinx Antoine Amarilli
2018-01-10 16:14 ` [PATCH 1/2] INSTALL: refer to python3-sphinx Daniel Kahn Gillmor
2018-01-10 16:14 ` [PATCH 2/2] travis: build against python3-sphinx instead of python-sphinx Daniel Kahn Gillmor
2018-01-10 17:09 ` [PATCH 1/2] INSTALL: refer to python3-sphinx David Bremner
2018-01-10 20:37 ` Daniel Kahn Gillmor
2018-01-10 19:46 ` Tomi Ollila
2018-01-13 1:01 ` David Bremner
2018-01-10 16:15 ` Daniel Kahn Gillmor [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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp0p3d2f.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=a3nm@a3nm.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).