From: "matz (Yukihiro Matsumoto) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "matz (Yukihiro Matsumoto)" <noreply@ruby-lang.org>
Subject: [ruby-core:112106] [Ruby master Misc#16671] BASERUBY version policy
Date: Mon, 30 Jan 2023 02:12:06 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-101543.20230130021205.17@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16671.20200304064036.17@ruby-lang.org
Issue #16671 has been updated by matz (Yukihiro Matsumoto).
I agree with upgrading BASERUBY. The version should be determined by the latest version of the distribution (Debian?).
Matz.
----------------------------------------
Misc #16671: BASERUBY version policy
https://bugs.ruby-lang.org/issues/16671#change-101543
* Author: ko1 (Koichi Sasada)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
Ruby 2.7 (MRI) requires Ruby 2.2 or later (== BASERUBY) to build from repository.
Tarball does not need any installed Ruby.
To build latest Ruby from repository, you need to build Ruby 2.2 and later from a tarball.
Can we make the BASERUBY version update policy?
# Background
To use `ISeq#to_a` (specific format) Ruby 2.2 or later is needed from Ruby 2.7.
The oldest version used by RubyCI machines was Ruby 2.2, so I determined update.
I needed to file a ticket about this version bump, sorry.
---
related: https://bugs.ruby-lang.org/issues/16668
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2023-01-30 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 6:40 [ruby-core:97355] [Ruby master Misc#16671] BASERUBY version policy ko1
2020-03-04 8:24 ` [ruby-core:97356] " naruse
2020-03-04 9:47 ` [ruby-core:97357] " nobu
2020-03-05 1:11 ` [ruby-core:97363] " shyouhei
2022-09-26 6:45 ` [ruby-core:110081] " hsbt (Hiroshi SHIBATA)
2023-01-06 4:48 ` [ruby-core:111669] " hsbt (Hiroshi SHIBATA) via ruby-core
2023-01-06 10:15 ` [ruby-core:111673] " nobu (Nobuyoshi Nakada) via ruby-core
2023-01-30 2:12 ` matz (Yukihiro Matsumoto) via ruby-core [this message]
2023-01-30 8:13 ` [ruby-core:112111] " vo.x (Vit Ondruch) via ruby-core
2023-01-30 8:27 ` [ruby-core:112112] " hsbt (Hiroshi SHIBATA) via ruby-core
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-101543.20230130021205.17@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.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.
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).