unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Polidoro <peter@polidoro.io>
To: jbranso@dismail.de
Cc: guix-devel@gnu.org, 55728@debbugs.gnu.org,
	Skyler Ferris <skyvine@protonmail.com>
Subject: [bug#55728] Handling expensive packages
Date: Tue, 12 Mar 2024 16:45:47 -0400	[thread overview]
Message-ID: <B22ACCA8-97D8-4516-854F-2A80EB9436D3@polidoro.io> (raw)
In-Reply-To: <4d42f1c112461bd6bb81420b9794c027d1f2e139@dismail.de>

You can ignore or delete this patch if it is causing problems.

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. 

Thanks!

> On Mar 12, 2024, at 15:59, jbranso@dismail.de wrote:
> Hey Peter!
> 
> Your patch found its way on onto the guix devel list!
> 
> Thanks for contributing to guix!  We want to add your patch, and we are wondering what your motivation was for sending this patch?  Is your patch a prerequisite for a package you want to add?  Or do you have some other reason?
> 
> Thanks,
> 
> Joshua
> https://gnucode.me




  reply	other threads:[~2024-03-12 20:46 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 [this message]
2024-03-13  0:15     ` Skyler Ferris
2024-03-13  0:15       ` [bug#55728] " 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=B22ACCA8-97D8-4516-854F-2A80EB9436D3@polidoro.io \
    --to=peter@polidoro.io \
    --cc=55728@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jbranso@dismail.de \
    --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).