From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: [PATCH 1/2] INSTALL: refer to python3-sphinx
Date: Wed, 10 Jan 2018 11:14:51 -0500 [thread overview]
Message-ID: <20180110161452.15172-1-dkg@fifthhorseman.net> (raw)
In-Reply-To: <20180110153000.jckdavxrom7ibhy4@zeta>
We're now preferring to build with python3 instead of python2. Update
the INSTALL to match.
Thanks to Antoine Amarilli <a3nm@a3nm.net> for pointing this out!
---
INSTALL | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/INSTALL b/INSTALL
index 875014f0..4a0dc741 100644
--- a/INSTALL
+++ b/INSTALL
@@ -88,11 +88,11 @@ dependencies with a simple simple command line. For example:
For Debian and similar:
- sudo apt-get install libxapian-dev libgmime-3.0-dev libtalloc-dev zlib1g-dev python-sphinx
+ sudo apt-get install libxapian-dev libgmime-3.0-dev libtalloc-dev zlib1g-dev python3-sphinx
For Fedora and similar:
- sudo yum install xapian-core-devel gmime-devel libtalloc-devel zlib-devel python-sphinx
+ sudo yum install xapian-core-devel gmime-devel libtalloc-devel zlib-devel python3-sphinx
On other systems, a similar command can be used, but the details of
the package names may be different.
--
2.15.1
next 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 ` Daniel Kahn Gillmor [this message]
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 ` Bug: INSTALL should mention python3-sphinx not python-sphinx Daniel Kahn Gillmor
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=20180110161452.15172-1-dkg@fifthhorseman.net \
--to=dkg@fifthhorseman.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).