From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 40029@debbugs.gnu.org
Subject: bug#40029: Preventing automatic python2 transformation of some packages
Date: Thu, 12 Mar 2020 14:04:35 +0100 [thread overview]
Message-ID: <87r1xxu3ks.fsf@gnu.org> (raw)
In-Reply-To: <87lfo6zqwp.fsf@devup.no> (Marius Bakke's message of "Wed, 11 Mar 2020 19:29:26 +0100")
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
Hi!
Marius Bakke <mbakke@fastmail.com> skribis:
> 'python2-sphinx' is obsolete and increasingly a maintenance burden,
> because we need to keep special versions around just to make it build.
>
> The only reason we have this package is because it gets pulled in
> automatically when using (package-with-python2 ...) on a Python 3
> package that has 'python-sphinx' in inputs.
What about this evil hack?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 582 bytes --]
diff --git a/gnu/packages/sphinx.scm b/gnu/packages/sphinx.scm
index 323d5b4457..66306e97fc 100644
--- a/gnu/packages/sphinx.scm
+++ b/gnu/packages/sphinx.scm
@@ -99,7 +99,7 @@
for Python projects or other documents consisting of multiple reStructuredText
sources.")
(license license:bsd-2)
- (properties `((python2-variant . ,(delay python2-sphinx))))))
+ (properties `((python2-variant . ,(delay python-sphinx))))))
;; Sphinx 2 does not support Python 2, so we stick with this older version here.
;; Remove this package once python2-pbcore no longer requires it.
[-- Attachment #3: Type: text/plain, Size: 144 bytes --]
The effect should be that ‘package-with-python2’ always keeps
‘python-sphinx’ unchanged. (It’s a double-edge sword.)
Ludo’.
next prev parent reply other threads:[~2020-03-12 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 18:29 bug#40029: Preventing automatic python2 transformation of some packages Marius Bakke
2020-03-12 12:19 ` Leo Prikler
2020-03-12 13:04 ` Ludovic Courtès [this message]
2020-07-25 19:05 ` Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1xxu3ks.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40029@debbugs.gnu.org \
--cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).