From: Christopher Rodriguez <yewscion@gmail.com>
To: 52684@debbugs.gnu.org
Subject: bug#52684: [BUG] Multiple Packages Failing to Build
Date: Sun, 2 Jan 2022 08:53:23 -0500 [thread overview]
Message-ID: <130d6b18-1b3e-af35-787a-722517e48987@gmail.com> (raw)
In-Reply-To: <7ee7ed76-4676-6c86-87f0-8d7ab886fc50@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1184 bytes --]
Hey Maxime,
The let form was mostly included because, if possible, we should pull
the value of `beets-python-version` from the version of python used for
beets (because this implementation currently relies on a hardcoded and
versioned library path in `lib/python3.9/site-packages`, it will require
maintenance that could otherwise be avoided if we pulled the version
from python directly.
However, I don't know how to do that, or if that is possible. If it's
not something easily doable, then I will remove the let form for now,
and see about improving it in the future.
As for the issue of other python libraries possibly polluting the beets
install, AFAIK beets looks for a folder named `beetsplug` in the
PYTHONPATH and only considers files beneath it. I think we can safely
avoid isolating the beets plugins; Whether this is the route Guix wants
to go is something I think should ideally be standardized across all
packages if possible (maybe an email thread on guix-devel?), because the
main channel as a whole will be more maintainable if we can come to some
kind of agreement.
Let me know what You think.
--
Christopher Rodriguez
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4045 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-01-02 13:54 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
2021-12-27 20:36 ` Christopher Rodriguez
2022-01-02 13:53 ` Christopher Rodriguez [this message]
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=130d6b18-1b3e-af35-787a-722517e48987@gmail.com \
--to=yewscion@gmail.com \
--cc=52684@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 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).