unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)
Date: Tue, 31 Aug 2021 10:19:48 +0000	[thread overview]
Message-ID: <6Lkh0w8XQq-H1fCCOf1Ag5SSJVyyYmZlorzV-EOjgU0uLwVcjrWnLioPQ5JKnY4On9u5KMNbTIW2EbsmoXnQOXkF-VycfQeBsZre3zHPxEc=@lendvai.name> (raw)
In-Reply-To: <IHcyl82Ui7MmWHcyHSrPEE-SnSjEaK_0wwbNDwYco242e3GksdryxgiTJ9_Wf6YqlDKkbRAy88dMlQYPzNW8qF8uGIAKnemTBJN48a1U3mM=@lendvai.name>

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

FTR, we had a discussion about this on IRC:

https://logs.guix.gnu.org/guix/2021-08-31.log#024401

conclusion:

ideally, Guix should have a pinned package for each go dependency, and with the go importer it's not hopeless to do anymore.

it conflicts with the general Guix policy to package the latest releases, so i'm putting all the pinned packages generated by `guix go import` into a separate go-ethereum.scm, and into a separate module.

any correction/guidance is welcome!

- attila
PGP: 5D5F 45C7 DFCD 0A39

[-- Attachment #2: Type: text/html, Size: 894 bytes --]

  reply	other threads:[~2021-08-31 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 21:52 packaging go-ethereum, and ultimately bee (of ethswarm.org) Attila Lendvai
2021-08-31 10:19 ` Attila Lendvai [this message]
2021-08-31 22:21 ` Maxime Devos
2021-09-01 14:29   ` Attila Lendvai
2021-09-01 16:17     ` Maxime Devos
2021-09-03  8:16       ` Attila Lendvai
2021-09-03 16:01         ` Bengt Richter
2021-09-03 19:51           ` Attila Lendvai
  -- strict thread matches above, loose matches on Subject: below --
2021-09-01 19:14 Sarah Morgensen

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='6Lkh0w8XQq-H1fCCOf1Ag5SSJVyyYmZlorzV-EOjgU0uLwVcjrWnLioPQ5JKnY4On9u5KMNbTIW2EbsmoXnQOXkF-VycfQeBsZre3zHPxEc=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=guix-devel@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).