From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/parser/
Date: Thu, 9 Mar 2023 15:10:06 +0000 (UTC) [thread overview]
Message-ID: <1678374164.cee0f540795944b167e6bb5e0199753b6be15253.graaff@gentoo> (raw)
commit: cee0f540795944b167e6bb5e0199753b6be15253
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 8 07:23:46 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Mar 9 15:02:44 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cee0f540
dev-ruby/parser: add 3.2.1.1
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/parser/Manifest | 1 +
dev-ruby/parser/parser-3.2.1.1.ebuild | 43 +++++++++++++++++++++++++++++++++++
2 files changed, 44 insertions(+)
diff --git a/dev-ruby/parser/Manifest b/dev-ruby/parser/Manifest
index 91d650a0e665..4d51e5d99fc8 100644
--- a/dev-ruby/parser/Manifest
+++ b/dev-ruby/parser/Manifest
@@ -4,3 +4,4 @@ DIST parser-3.1.2.1.tar.gz 299885 BLAKE2B 2fe56279be003825a25e6fdfc99dbb13b93dc1
DIST parser-3.1.3.0.tar.gz 301000 BLAKE2B 3b7984966643d983e8606ba4de13a08de9130aa58b5adebdc9cfb273e00e700086f99f8a678ccb6db1ac70dac2da429dbfa1b45661c4f9764b676beae5c64633 SHA512 23ef12043706ba810ade3ac94f376082d5b45db8b451634d469a26f834890e7a82a9669132df4654aef4cb7650f0e13d2f33aad489ebbbb76ab547cb9e64f498
DIST parser-3.2.0.0.tar.gz 302043 BLAKE2B 8a02ca62560fc976fbe62d02ecf24713248a9f522e1cc9daa1deaa153d900628dce4f59c7791cc61652199358addca1432403a3f3849b0ef8f9495639282697d SHA512 58b9011c22af76f5eccf7035dd53da705ddc952c6185ebbb48c33c5486b5852ba8a543093f8c1f2a2c7aea8e78407c04a9dc49abf43edb27c460cf8b038338cf
DIST parser-3.2.1.0.tar.gz 315249 BLAKE2B 57013e299541e0b1d589be8640611c3deb04b11cd39ada33dd2ae0b43fa68b7ffa55d6074d53559a2a5f552e539bf80ea7406a91e4b5dbc7fae345d9d399bc09 SHA512 f79f84188650a210424558c9f0d131de25ea7d879487331db9d5a55127fd72e28946a78f7596896bd837b4b17e8602b908fc818f467f77cee04c4ffdce545f76
+DIST parser-3.2.1.1.tar.gz 315592 BLAKE2B 5e783269d367fc9f2e98f5bcb038c8f835a930bd3664769da30441a1525908f96c9fa9cb23c42d07614a550d327c406470f59696a22cc58f57c087c3a09a9967 SHA512 ba9077e11864ba816d04f77f1160f46ad697c5a0751ac6991758259054754fdfda59e762c8df5e66d6ddb28ddd561713ba15a11a67d61024180f7e375ac112f1
diff --git a/dev-ruby/parser/parser-3.2.1.1.ebuild b/dev-ruby/parser/parser-3.2.1.1.ebuild
new file mode 100644
index 000000000000..1831dac09aaf
--- /dev/null
+++ b/dev-ruby/parser/parser-3.2.1.1.ebuild
@@ -0,0 +1,43 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+USE_RUBY="ruby27 ruby30 ruby31"
+
+RUBY_FAKEGEM_RECIPE_DOC="yard"
+RUBY_FAKEGEM_TASK_TEST="test"
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
+
+RUBY_FAKEGEM_VERSION="${PV/_pre/.pre.}"
+
+RUBY_FAKEGEM_GEMSPEC="parser.gemspec"
+
+inherit ruby-fakegem
+
+DESCRIPTION="A production-ready Ruby parser written in pure Ruby"
+HOMEPAGE="https://github.com/whitequark/parser"
+SRC_URI="https://github.com/whitequark/parser/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~sparc"
+IUSE=""
+
+DEPEND+=" =dev-util/ragel-6*"
+
+ruby_add_bdepend "
+ test? (
+ dev-ruby/minitest:5
+ dev-ruby/racc )
+ dev-ruby/cliver
+"
+ruby_add_rdepend "=dev-ruby/ast-2.4* >=dev-ruby/ast-2.4.1"
+
+all_ruby_prepare() {
+ sed -i -e "/[Bb]undler/d" Rakefile || die
+ sed -i -e '/simplecov/ s:^:#:' test/helper.rb || die
+}
+
+each_ruby_compile() {
+ ${RUBY} -S rake generate || die
+}
next reply other threads:[~2023-03-09 15:10 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 15:10 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 5:58 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/parser/ Hans de Graaff
2025-02-07 5:58 Hans de Graaff
2025-01-17 7:04 Hans de Graaff
2024-11-07 7:22 Hans de Graaff
2024-11-03 6:38 Hans de Graaff
2024-11-03 6:38 Hans de Graaff
2024-09-06 4:59 Hans de Graaff
2024-08-09 7:08 Hans de Graaff
2024-08-08 4:41 Hans de Graaff
2024-08-08 4:41 Hans de Graaff
2024-07-11 5:38 Hans de Graaff
2024-06-13 5:50 Hans de Graaff
2024-05-31 6:15 Hans de Graaff
2024-05-31 6:15 Hans de Graaff
2024-04-27 7:43 Hans de Graaff
2024-02-11 7:26 Hans de Graaff
2024-02-02 7:01 Hans de Graaff
2024-01-20 8:44 Hans de Graaff
2024-01-20 8:44 Hans de Graaff
2024-01-13 8:30 Hans de Graaff
2024-01-13 8:30 Hans de Graaff
2024-01-07 8:26 Hans de Graaff
2024-01-06 8:19 Hans de Graaff
2023-10-05 6:07 Hans de Graaff
2023-07-11 7:47 Hans de Graaff
2023-06-09 8:21 Hans de Graaff
2023-04-25 5:06 Hans de Graaff
2023-04-01 9:00 Hans de Graaff
2023-04-01 9:00 Hans de Graaff
2023-02-10 7:45 Hans de Graaff
2023-01-08 7:49 Hans de Graaff
2022-12-04 15:08 Hans de Graaff
2022-11-28 7:01 Hans de Graaff
2022-08-09 5:46 Hans de Graaff
2022-06-25 9:29 Hans de Graaff
2022-04-13 5:41 Hans de Graaff
2022-04-02 8:57 Hans de Graaff
2022-02-22 18:50 Hans de Graaff
2022-01-08 11:47 Hans de Graaff
2021-12-10 6:56 Hans de Graaff
2021-12-01 17:57 Hans de Graaff
2021-11-26 6:31 Hans de Graaff
2021-11-26 6:31 Hans de Graaff
2021-07-10 6:23 Hans de Graaff
2021-05-29 7:47 Hans de Graaff
2021-05-07 6:00 Hans de Graaff
2021-04-08 6:07 Hans de Graaff
2021-02-07 8:32 Hans de Graaff
2021-02-07 8:32 Hans de Graaff
2020-10-16 9:33 Hans de Graaff
2020-10-14 4:24 Hans de Graaff
2020-10-13 4:18 Hans de Graaff
2020-10-07 4:48 Hans de Graaff
2020-09-25 6:09 Hans de Graaff
2020-09-11 5:14 Hans de Graaff
2020-06-21 4:29 Hans de Graaff
2020-06-01 5:30 Hans de Graaff
2020-06-01 5:30 Hans de Graaff
2020-05-24 6:46 Hans de Graaff
2020-05-01 4:58 Hans de Graaff
2020-04-17 4:39 Hans de Graaff
2020-04-05 5:02 Hans de Graaff
2020-03-22 10:01 Hans de Graaff
2020-03-22 10:01 Hans de Graaff
2020-03-03 7:25 Hans de Graaff
2020-02-27 6:05 Hans de Graaff
2020-01-09 5:51 Hans de Graaff
2020-01-09 5:51 Hans de Graaff
2019-12-31 6:55 Hans de Graaff
2019-12-27 6:22 Hans de Graaff
2019-11-09 6:28 Hans de Graaff
2019-10-03 6:07 Hans de Graaff
2019-09-12 5:54 Hans de Graaff
2019-09-03 4:25 Hans de Graaff
2019-09-03 4:25 Hans de Graaff
2019-04-29 5:32 Hans de Graaff
2019-04-06 6:16 Hans de Graaff
2019-04-06 6:16 Hans de Graaff
2019-03-24 8:35 Hans de Graaff
2019-02-14 6:44 Hans de Graaff
2019-01-17 5:26 Hans de Graaff
2018-11-08 5:35 Hans de Graaff
2018-11-08 5:35 Hans de Graaff
2018-07-13 6:12 Hans de Graaff
2018-07-13 6:12 Hans de Graaff
2018-07-10 4:13 Hans de Graaff
2018-07-10 4:13 Hans de Graaff
2018-04-18 5:09 Hans de Graaff
2018-03-25 7:04 Hans de Graaff
2018-03-07 17:20 Hans de Graaff
2018-03-05 5:55 Hans de Graaff
2018-02-17 7:34 Hans de Graaff
2018-02-08 6:25 Hans de Graaff
2017-11-18 6:58 Hans de Graaff
2017-06-14 5:15 Hans de Graaff
2017-02-08 6:02 Hans de Graaff
2017-02-08 6:02 Hans de Graaff
2016-12-14 7:15 Hans de Graaff
2016-11-30 7:30 Hans de Graaff
2016-11-30 7:30 Hans de Graaff
2016-11-21 6:01 Hans de Graaff
2016-09-20 5:07 Hans de Graaff
2016-09-18 5:46 Hans de Graaff
2016-09-18 5:46 Hans de Graaff
2016-06-02 5:16 Hans de Graaff
2016-04-27 11:54 Hans de Graaff
2016-04-27 11:54 Hans de Graaff
2016-03-30 5:29 Hans de Graaff
2016-02-17 22:28 Manuel Rüger
2016-02-17 22:28 Manuel Rüger
2016-02-11 1:13 Manuel Rüger
2016-02-11 1:13 Manuel Rüger
2016-01-31 14:11 Hans de Graaff
2016-01-15 6:41 Hans de Graaff
2015-10-09 6:08 Hans de Graaff
2015-10-09 6:08 Hans de Graaff
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1678374164.cee0f540795944b167e6bb5e0199753b6be15253.graaff@gentoo \
--to=graaff@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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