From: Skyler Ferris via Guix-patches via <guix-patches@gnu.org>
To: Peter Polidoro <peter@polidoro.io>, jbranso@dismail.de
Cc: guix-devel@gnu.org, 55728@debbugs.gnu.org
Subject: [bug#55728] Handling expensive packages
Date: Wed, 13 Mar 2024 00:15:20 +0000 [thread overview]
Message-ID: <0aea0990-046d-4759-818b-e8380d5147b1@protonmail.com> (raw)
Message-ID: <20240313001520.4_NHfomJhdrszlEusUrqgC3oL4kQXSmwxCCWI8im6rE@z> (raw)
In-Reply-To: <B22ACCA8-97D8-4516-854F-2A80EB9436D3@polidoro.io>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On 3/12/24 13:45, Peter Polidoro wrote:
> If I remember correctly, that was a patch I submitted a couple of years ago when I was attempting to package some embedded software tools, either the zephyr west tool or platformio, both written in python. That sent me down the rabbit hole of dependency updates, the python-mock package being one of them.
>
> I would still love to have both west and platformio packaged in guix. Perhaps those exist now in Guix or another channel, I have not checked in a while. If not, I will attempt to package them again at some point.
Thank you for the information. I see that west is packaged in gnu/packages/embedded.scm, but the only reference to platformio is an emacs plugin which I suspect is not what you are referring to. So it sounds like there is no particular reason to process this patch immediately but it makes sense to leave open because it might be used down the line.
[-- Attachment #2: Type: text/html, Size: 1300 bytes --]
next prev parent reply other threads:[~2024-03-13 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 19:06 Handling expensive packages Skyler Ferris
2024-03-12 19:59 ` [bug#55728] " jbranso--- via Guix-patches via
2024-03-12 20:45 ` Peter Polidoro
2024-03-13 0:15 ` Skyler Ferris [this message]
2024-03-13 0:15 ` Skyler Ferris via Guix-patches via
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=0aea0990-046d-4759-818b-e8380d5147b1@protonmail.com \
--to=guix-patches@gnu.org \
--cc=55728@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.de \
--cc=peter@polidoro.io \
--cc=skyvine@protonmail.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).