unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: 46266@debbugs.gnu.org
Subject: [bug#46266] [PATCH] gnu: Update bitcoin-core to 0.21.0
Date: Wed, 24 Feb 2021 09:11:57 +0000	[thread overview]
Message-ID: <877dmxltia.fsf@cbaines.net> (raw)
In-Reply-To: <kIOle-DVD92QUejpS8kaieqldVYP0h7LdOG6a5E5PjbyNkgA9ktKR3Ryz71GXxcfdPVMLya3CtveEKDFx5_NQ5hKZ1m1a5GsE6P8pjTOpSw=@protonmail.com>

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


Hi ZmnSCPxj,

Sorry for the delay in getting back to you.

guix-patches--- via <guix-patches@gnu.org> writes:

> In addition to updating, I made as well, separate `bitcoin-core-0.20`
> and `bitcoin-core-0.21` packages.  Due to RPC changes, it is possible
> that other programs compatible with older `bitcoin-core` version is
> not compatible with newer version.  Thus, an `operating-system`
> declaration, may need to pin a specific major version.

I think it's OK to keep older versions if that's important, but it would
be good to specifically note why specific older versions are useful to
keep. I'm saying that because it's useful to know when an older version
can be removed. So, for 0.20 are there incompatibilities that you're
aware of?

The second thing is, I wouldn't immediately jump to the
(make-... pattern, and I would instead use package inheritance. See the
ruby packages for example [1].

1: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/ruby.scm#n95

Package inheritance makes it simpler to make changes to individual
versions, and avoids the complexity of introducing a procedure.

Does that all make sense?

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2021-02-24  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  2:54 [bug#46266] [PATCH] gnu: Update bitcoin-core to 0.21.0 guix-patches--- via
2021-02-24  9:11 ` Christopher Baines [this message]
2021-03-16  2:53   ` ZmnSCPxj via Guix-patches via
2021-03-16 23:42     ` Christopher Baines
2021-03-17  3:18       ` ZmnSCPxj via Guix-patches via
2021-03-17 11:48 ` [bug#46266] [PATCH v2] " ZmnSCPxj via Guix-patches via
2021-03-23 21:59   ` bug#46266: " Christopher Baines

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=877dmxltia.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=46266@debbugs.gnu.org \
    --cc=ZmnSCPxj@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).