unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: "51471-close@debbugs.gnu.org" <51471-close@debbugs.gnu.org>
Subject: bug#51471: [PATCH] gnu: Add geth-binary.
Date: Fri, 29 Oct 2021 19:31:44 +0000	[thread overview]
Message-ID: <ZPwzpqFqgBFyIr50O6hxhyv9v-UbuVlUztq66wu-tM7OjvvG3udMRF8kDGj57eVB1Se7uorpM1aV-WznzN7hQIVAgtYZ9qZ4_hw7laYjuaE=@lendvai.name> (raw)
In-Reply-To: <875ytgp5bm.fsf@kitej>

ok, i'll file it somewhere else.

thanks for the quick feedback,

- attila
PGP: 5D5F 45C7 DFCD 0A39

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, October 29th, 2021 at 10:51, Guillaume Le Vaillant <glv@posteo.net> wrote:

> Attila Lendvai attila@lendvai.name skribis:
>
> > It downloads, verifies, and patches the official binary release of the
> >
> > go-ethereum client using patchelf.
> >
> > -   gnu/packages/geth-binary.scm (geth-binary): New variable.
> >
> > dear fellow Guix hackers,
> >
> > RFC: would Guix accept a package like this? if yes, then i welcome any
> >
> > feedback, this is my first binary package. i welcome also pointers to
> >
> > other packages from which i should mimic something.
> >
> > this is only lightly tested for now, but before i tidy everything up,
> >
> > i wanted to know whether such a beast would ever be accepted.
>
> Hi,
>
> The official Guix repository can only include free software built from
>
> sources. For a package definition downloading a binary, you have to use
>
> a custom channel [1].
>
> [1] https://guix.gnu.org/manual/devel/en/guix.html#Channels




      reply	other threads:[~2021-10-29 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  1:22 [bug#51471] [PATCH] gnu: Add geth-binary Attila Lendvai
2021-10-29  8:51 ` Guillaume Le Vaillant
2021-10-29 19:31   ` Attila Lendvai [this message]

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='ZPwzpqFqgBFyIr50O6hxhyv9v-UbuVlUztq66wu-tM7OjvvG3udMRF8kDGj57eVB1Se7uorpM1aV-WznzN7hQIVAgtYZ9qZ4_hw7laYjuaE=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=51471-close@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).