unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Ryan Prior <rprior@protonmail.com>
Cc: 41036-done@debbugs.gnu.org
Subject: bug#41036: [PATCH 0/2] New patches to update Ruby to 2.7
Date: Wed, 24 Jun 2020 21:28:51 +0100	[thread overview]
Message-ID: <87eeq46we4.fsf@cbaines.net> (raw)
In-Reply-To: <20200621030211.21346-1-rprior@protonmail.com>

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


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

> Here are the new patches you asked for, they should apply cleanly to master.
>
> Ryan Prior (2):
>   gnu: Renames ruby to ruby-2.6.
>   gnu: Ruby: Update to 2.7.
>
>  gnu/packages/ruby.scm | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)

Great, thanks.

I've tweaked the commit messages a bit, and now pushed these patches to
core-updates.

I think the way ruby-2.7 inherits from ruby-2.6 is a bit odd, but I like
that this change is small in terms of the diff. Anyway, how to lay out
the package definitions is a lesser issue compared to what's actually
defined.

Now comes the challenge of actually fixing all the packages this change
will have broken. If updates to packages that fix issues with Ruby 2.7
don't cause too many rebuilds or break anything on master, then pushing
those to master is good. The master branch can then be merged in to
core-updates to get those changes applied there as well. Otherwise, the
fixes should be applied to core-updates.

Thanks,

Chris

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

      parent reply	other threads:[~2020-06-24 20:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 23:25 [bug#41036] ruby: Add 2.7.3 Ryan Prior via Guix-patches via
2020-05-02 23:34 ` [bug#41036] ruby: Add ruby-2.5 as an alias to ruby Ryan Prior via Guix-patches via
2020-05-02 23:34 ` [bug#41036] ruby: Update to 2.7.3 Ryan Prior via Guix-patches via
2020-05-07  7:47   ` Ludovic Courtès
2020-05-07 19:27     ` Ryan Prior via Guix-patches via
2020-05-12  8:10       ` Diego Nicola Barbato
2020-05-12 12:47   ` [bug#41036] [EXT] " Thompson, David
2020-05-12 17:55     ` Ryan Prior via Guix-patches via
2020-05-13 17:54 ` [bug#41036] ruby: Add 2.7.3 Christopher Baines
2020-06-17 10:03   ` Ludovic Courtès
2020-06-19  8:54     ` Christopher Baines
2020-06-21  3:02 ` [bug#41036] [PATCH 0/2] New patches to update Ruby to 2.7 Ryan Prior via Guix-patches via
2020-06-21  3:02   ` [bug#41036] [PATCH 1/2] gnu: Renames ruby to ruby-2.6 Ryan Prior via Guix-patches via
2020-06-21  3:02   ` [bug#41036] [PATCH 2/2] gnu: Ruby: Update to 2.7 Ryan Prior via Guix-patches via
2020-06-24 20:28   ` Christopher Baines [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=87eeq46we4.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=41036-done@debbugs.gnu.org \
    --cc=rprior@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).