From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/regexp_parser/
Date: Fri, 18 Mar 2022 06:57:53 +0000 (UTC) [thread overview]
Message-ID: <1647586654.e4c547818d63a0730738f3061f4505a8b9bcc1ef.graaff@gentoo> (raw)
commit: e4c547818d63a0730738f3061f4505a8b9bcc1ef
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 18 06:57:34 2022 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Mar 18 06:57:34 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e4c54781
dev-ruby/regexp_parser: add 2.2.1
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/regexp_parser/Manifest | 1 +
dev-ruby/regexp_parser/regexp_parser-2.2.1.ebuild | 36 +++++++++++++++++++++++
2 files changed, 37 insertions(+)
diff --git a/dev-ruby/regexp_parser/Manifest b/dev-ruby/regexp_parser/Manifest
index c529073f6fd2..7c55be7551e4 100644
--- a/dev-ruby/regexp_parser/Manifest
+++ b/dev-ruby/regexp_parser/Manifest
@@ -2,3 +2,4 @@ DIST regexp_parser-0.5.0.tar.gz 80554 BLAKE2B 7890e6850e3ffbb927c5e72430ab29e6ae
DIST regexp_parser-1.8.2.tar.gz 85592 BLAKE2B 55333dbf59606d1f203c84cc3e712ddba9551be492745f2a0ce9ca8ba56e9a6eb1aee0c9d3d5079114c65747746f6ef4df3cbbf5a917562f413ca3426fd16efc SHA512 8192ee4334d2da13af5552eccd4fed82b24ed57489e3e0d8d083e8cf72e52fa185c2e007e9adf1ec6e59b0cf4e4055eb8def28d5cc94cc7a9ab7981d14f8e727
DIST regexp_parser-2.1.1.tar.gz 89399 BLAKE2B 7632b1e65e929f610e6bedc7954f81ca080f4f290794da617dbaeaae324186581a6e0ab78fb8d7311c33876b8cce090fdb6d4b868eeb80b82fa8461da5d82bfe SHA512 809b8c5f7bcceb0c31e97256d5a40a04bb7919cfa0a139e972e90a72ba15eee6dce8ac1f8e65f5e8f7a5f992a2fab91d6ae19f27a1f5ec7795fcc082ff037e13
DIST regexp_parser-2.2.0.tar.gz 89763 BLAKE2B 31fc5a5f9dcde1905bf515e8b7628a1e73a7a9f0a46ea7ec345bc4495c6293ba96395ee74b346fccf81ac45667a5ba7da6f764551ecf17fcc33376878f2b05a6 SHA512 db68850e794a691bcf04e49720e03bf0ee10b3c734cf85213940192f311d30d28b55093c7e35336e778d860df712a75e84b653d6042522c3ff3089f592849449
+DIST regexp_parser-2.2.1.tar.gz 90169 BLAKE2B dcfa392bc5dc9e08816b3a2e401744c775a8a5c60067c410d195d60ef155eba287b31243e70677f018e3d751b371a8878933a5e34c4bd5b00cef3bf1b266c00a SHA512 a3a6fbd36e980eaf5f14d0c98c2680aed700b01c7941fbc4e406e14992e432b3ce1510a8be9ef7964ddf0ab85c55b556206cdea36a336de98e6956942b4ff726
diff --git a/dev-ruby/regexp_parser/regexp_parser-2.2.1.ebuild b/dev-ruby/regexp_parser/regexp_parser-2.2.1.ebuild
new file mode 100644
index 000000000000..2f0645cf125d
--- /dev/null
+++ b/dev-ruby/regexp_parser/regexp_parser-2.2.1.ebuild
@@ -0,0 +1,36 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+USE_RUBY="ruby26 ruby27 ruby30"
+
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_BINWRAP=""
+
+RUBY_FAKEGEM_GEMSPEC="regexp_parser.gemspec"
+
+inherit ruby-fakegem
+
+DESCRIPTION="A library for tokenizing, lexing, and parsing Ruby regular expressions"
+HOMEPAGE="https://github.com/ammar/regexp_parser"
+SRC_URI="https://github.com/ammar/regexp_parser/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86"
+IUSE=""
+
+DEPEND+=" =dev-util/ragel-6*"
+
+ruby_add_bdepend "dev-ruby/rake
+ test? ( dev-ruby/ice_nine dev-ruby/regexp_property_values dev-ruby/rspec:3 )"
+
+all_ruby_prepare() {
+ sed -i -e '/bundler/I s:^:#:' Rakefile || die
+}
+
+each_ruby_compile() {
+ ${RUBY} -S rake ragel:rb || die
+}
next reply other threads:[~2022-03-18 6:57 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 6:57 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-16 10:09 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/regexp_parser/ Hans de Graaff
2025-08-13 6:13 Hans de Graaff
2025-08-09 7:56 Hans de Graaff
2025-08-09 7:56 Hans de Graaff
2025-08-04 5:49 Hans de Graaff
2025-06-02 10:48 Hans de Graaff
2025-05-20 18:31 Arthur Zamarin
2025-04-03 11:48 Hans de Graaff
2025-01-09 7:18 Hans de Graaff
2024-12-26 6:19 Hans de Graaff
2024-10-06 11:11 Sam James
2024-05-23 6:13 Hans de Graaff
2024-05-12 5:03 Hans de Graaff
2024-03-17 6:13 Hans de Graaff
2024-01-15 3:32 Ionen Wolkens
2024-01-09 7:44 Hans de Graaff
2024-01-01 8:07 Hans de Graaff
2024-01-01 8:07 Hans de Graaff
2024-01-01 8:07 Hans de Graaff
2023-12-05 7:14 Hans de Graaff
2023-10-11 5:37 Hans de Graaff
2023-08-29 14:50 Hans de Graaff
2023-08-13 5:22 Hans de Graaff
2023-03-26 7:19 Hans de Graaff
2023-03-26 7:19 Hans de Graaff
2023-02-18 7:29 Hans de Graaff
2023-01-21 7:20 Hans de Graaff
2022-11-26 16:08 Hans de Graaff
2022-11-26 16:08 Hans de Graaff
2022-10-01 7:06 Hans de Graaff
2022-07-01 7:36 Hans de Graaff
2022-06-24 7:39 Hans de Graaff
2022-05-29 6:20 Hans de Graaff
2022-05-29 6:20 Hans de Graaff
2022-05-29 6:20 Hans de Graaff
2022-05-10 5:00 Hans de Graaff
2022-05-10 5:00 Hans de Graaff
2022-04-25 5:23 Hans de Graaff
2022-04-23 8:01 Hans de Graaff
2022-04-09 7:38 Hans de Graaff
2022-04-02 8:57 Hans de Graaff
2022-04-02 8:57 Hans de Graaff
2021-12-05 7:24 Hans de Graaff
2021-10-10 23:45 Sam James
2021-09-07 21:28 Marek Szuba
2021-07-24 15:22 Sam James
2021-06-07 6:20 Sergei Trofimovich
2021-06-04 8:22 Hans de Graaff
2021-05-25 18:01 Sergei Trofimovich
2021-05-25 10:48 Sam James
2021-05-25 10:47 Sam James
2021-05-24 17:22 Sergei Trofimovich
2021-05-18 6:04 Hans de Graaff
2021-05-18 6:04 Hans de Graaff
2021-02-26 6:00 Hans de Graaff
2021-02-23 7:01 Hans de Graaff
2021-01-03 8:05 Hans de Graaff
2020-12-20 19:14 Sam James
2020-12-20 19:03 Sam James
2020-12-02 7:09 Hans de Graaff
2020-12-02 7:09 Hans de Graaff
2020-12-02 7:09 Hans de Graaff
2020-12-02 7:09 Hans de Graaff
2020-10-12 5:19 Hans de Graaff
2020-10-02 5:15 Hans de Graaff
2020-09-25 6:09 Hans de Graaff
2020-09-09 9:28 Hans de Graaff
2020-09-09 9:28 Hans de Graaff
2020-06-16 4:53 Hans de Graaff
2020-04-21 21:06 Sergei Trofimovich
2020-04-21 21:06 Sergei Trofimovich
2020-04-21 21:06 Sergei Trofimovich
2020-03-06 7:10 Hans de Graaff
2020-02-24 6:27 Hans de Graaff
2020-01-27 6:40 Hans de Graaff
2019-07-22 21:06 Hans de Graaff
2019-07-22 16:56 Aaron Bauman
2019-07-17 6:01 Hans de Graaff
2019-07-17 6:01 Hans de Graaff
2019-07-09 23:11 Sergei Trofimovich
2019-07-08 11:50 Hans de Graaff
2019-05-24 7:06 Hans de Graaff
2019-05-24 7:06 Hans de Graaff
2019-05-23 5:39 Hans de Graaff
2019-05-16 4:32 Hans de Graaff
2019-04-27 6:06 Hans de Graaff
2019-04-27 6:06 Hans de Graaff
2019-04-04 5:09 Hans de Graaff
2019-01-05 9:48 Hans de Graaff
2018-11-26 19:23 Mikle Kolyada
2018-11-17 23:18 Thomas Deutschmann
2018-11-17 23:18 Thomas Deutschmann
2018-11-15 7:24 Hans de Graaff
2018-11-12 6:14 Hans de Graaff
2018-10-26 5:13 Hans de Graaff
2018-07-29 7:04 Hans de Graaff
2018-05-15 5:15 Hans de Graaff
2018-02-09 6:58 Hans de Graaff
2018-02-09 6:58 Hans de Graaff
2017-09-23 6:13 Hans de Graaff
2017-07-21 6:29 Hans de Graaff
2017-07-21 6:29 Hans de Graaff
2017-04-07 5:45 Hans de Graaff
2017-01-15 9:23 Hans de Graaff
2016-12-20 6:00 Hans de Graaff
2016-10-16 18:22 Manuel Rüger
2016-10-16 18:21 Manuel Rüger
2016-01-16 7:04 Hans de Graaff
2015-09-20 6:31 Hans de Graaff
2015-09-07 21:56 Richard Farina
2015-09-05 6:06 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=1647586654.e4c547818d63a0730738f3061f4505a8b9bcc1ef.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