From: Maxime Devos <maximedevos@telenet.be>
To: Christopher Rodriguez <yewscion@gmail.com>, 52684@debbugs.gnu.org
Subject: bug#52684: [BUG] Multiple Packages Failing to Build
Date: Thu, 30 Dec 2021 10:29:48 +0000 [thread overview]
Message-ID: <20897e4173cb524ae98347ed2229364be3e6246d.camel@telenet.be> (raw)
In-Reply-To: <ebf1721f-d941-9b3e-bb39-fa1cef82d5e9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Christopher Rodriguez schreef op ma 27-12-2021 om 13:18 [-0500]:
+ (native-search-paths
+ ;; XXX: Attempting to use (package-native-search-paths python)
here would
+ ;; cause an error about python being an unbound variable in the
+ ;; tests. Instead, we set and use an explicit python version.
This error doesn't have anything to do with profiles, but with import
cycles between modules and native-search-paths not being thunked.
+ (list
+ (search-path-specification
+ (variable "GUIX_BEETSPLUGINPATH")
+ (separator #f)
+ (files (list (string-append "lib/python" beets-python-version
"/site-packages"))))))
A downside of this approach, is that 'GUIX_BEETSPLUGINPATH' would
include unrelated python libraries. I don't know if this would be an
actual problem in practice. This could be resolved by installing beets
libraries to a non-standard location, say
"lib/beets-dependencies/site-packages".
The 'python-build-system' probably won't expect this, but that could be
resolved by adding things from "lib/beets-dependencies/site-packages"
to 'GUIX_PYTHONPATH' in a build phase.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-12-30 10:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 19:17 bug#52684: [BUG] Multiple Packages Failing to Build Christopher Rodriguez
2021-12-21 0:36 ` zimoun
2021-12-21 17:52 ` Christopher Rodriguez
2021-12-21 18:02 ` Maxime Devos
2021-12-21 18:08 ` Christopher Rodriguez
2021-12-21 19:47 ` Christopher Rodriguez
2021-12-21 20:44 ` Maxime Devos
2021-12-21 21:38 ` Christopher Rodriguez
2021-12-21 22:38 ` Maxime Devos
2021-12-22 17:07 ` Christopher Rodriguez
2021-12-22 17:36 ` Maxime Devos
2021-12-22 19:59 ` Christopher Rodriguez
2021-12-22 20:50 ` Maxime Devos
2021-12-22 20:54 ` Maxime Devos
2021-12-22 21:57 ` Christopher Rodriguez
2021-12-23 9:27 ` Maxime Devos
2021-12-22 20:53 ` Maxime Devos
2021-12-27 18:18 ` Christopher Rodriguez
2021-12-27 20:06 ` Maxime Devos
2021-12-30 10:20 ` Maxime Devos
2021-12-30 10:29 ` Maxime Devos [this message]
2021-12-27 20:36 ` Christopher Rodriguez
2022-01-02 13:53 ` Christopher Rodriguez
2022-06-23 0:58 ` bug#52684: [PATCH v1] Updated and fixed frotz package Christopher Rodriguez
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=20897e4173cb524ae98347ed2229364be3e6246d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52684@debbugs.gnu.org \
--cc=yewscion@gmail.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).