From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 52595@debbugs.gnu.org
Subject: [bug#52595] [PATCH 2/5] gnu: python2-renpy: Do not delete non-existing file.
Date: Fri, 17 Dec 2021 19:22:04 +0100 [thread overview]
Message-ID: <8b5e080f294063890294937ca0eb96f41e4c9fdc.camel@gmail.com> (raw)
In-Reply-To: <9af1bb4930763c511306573bbf032d6ed700ff25.camel@gmail.com>
* gnu/packages/game-development.scm (python2-renpy)[build]: Don't delete
renpy/__init__.pyc, it is no longer being built. Adjust comment accordingly.
---
gnu/packages/game-development.scm | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/game-development.scm b/gnu/packages/game-development.scm
index 19d5e71506..fb8744382c 100644
--- a/gnu/packages/game-development.scm
+++ b/gnu/packages/game-development.scm
@@ -1317,9 +1317,8 @@ (define-public python2-renpy
;; named "setup.py".
(with-directory-excursion "module"
(apply (assoc-ref %standard-phases 'build) args))
- ;; the above causes renpy.__init__ to be compiled but does not
- ;; compile anything else, hence we do that here
- (delete-file "renpy/__init__.pyc")
+ ;; The above only builds the cython modules, but nothing else,
+ ;; so we do that here.
(invoke "python" "-m" "compileall" "renpy")
#t))
(replace 'install
--
2.34.0
next prev parent reply other threads:[~2021-12-18 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 19:52 [bug#52595] [PATCH 0/5] Update Ren'py to 7.4.11 Liliana Marie Prikler
2021-12-17 17:56 ` [bug#52595] [PATCH 1/5] gnu: python-future: Fix sanity check Liliana Marie Prikler
2021-12-17 18:22 ` Liliana Marie Prikler [this message]
2021-12-17 18:59 ` [bug#52595] [PATCH 3/5] gnu: renpy: Move renpy command to aux-files Liliana Marie Prikler
2021-12-17 19:31 ` [bug#52595] [PATCH 4/5] gnu: python2-pygame-sdl2: Update to renpy version 7.4.11 Liliana Marie Prikler
2021-12-17 19:32 ` [bug#52595] [PATCH 5/5] gnu: python2-renpy: Update to 7.4.11 Liliana Marie Prikler
2022-01-15 9:02 ` bug#52595: " Liliana Marie Prikler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b5e080f294063890294937ca0eb96f41e4c9fdc.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=52595@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.