public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
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: Sun,  3 Jan 2021 08:05:31 +0000 (UTC)	[thread overview]
Message-ID: <1609661123.822348dc6d830fc32aca782ccf07d31a4a22b879.graaff@gentoo> (raw)

commit:     822348dc6d830fc32aca782ccf07d31a4a22b879
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Jan  3 07:23:50 2021 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Jan  3 08:05:23 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=822348dc

dev-ruby/regexp_parser: add 2.0.3

Package-Manager: Portage-3.0.12, Repoman-3.0.2
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/regexp_parser/Manifest                   |  1 +
 dev-ruby/regexp_parser/regexp_parser-2.0.3.ebuild | 37 +++++++++++++++++++++++
 2 files changed, 38 insertions(+)

diff --git a/dev-ruby/regexp_parser/Manifest b/dev-ruby/regexp_parser/Manifest
index f3595428513..fa55a228831 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.7.1.tar.gz 83865 BLAKE2B 1aab4f5c4d399ee48951a9fa9f24fef14073ca5267ec29e5011880274d2749a7a3d1f5cb2a6a5107d5c848537367e1f725a6de9bb9af8803ccc8ccedaac415eb SHA512 fda810bc18039484725df5c6092b3d1b31f398e337cbace253cfdfa934274902f2dcb4e64c4fd0bb24379c79ea2976383313c1a5cd4ad246ecb7eabfd1a47d64
 DIST regexp_parser-1.8.2.tar.gz 85592 BLAKE2B 55333dbf59606d1f203c84cc3e712ddba9551be492745f2a0ce9ca8ba56e9a6eb1aee0c9d3d5079114c65747746f6ef4df3cbbf5a917562f413ca3426fd16efc SHA512 8192ee4334d2da13af5552eccd4fed82b24ed57489e3e0d8d083e8cf72e52fa185c2e007e9adf1ec6e59b0cf4e4055eb8def28d5cc94cc7a9ab7981d14f8e727
 DIST regexp_parser-2.0.0.tar.gz 85985 BLAKE2B 6d206de85e85cd5f3f472f6b2cba49bc03aa43fc246af145188c2ebfe3da1c23e0b8b5d307d8902662abcd220b3c7a439825ada2012a09fdfffd9c390865a0d3 SHA512 a896f81988c8fb8074e05abe6c9723a314b147ac2098d11324842b79a8b74ae3a8237ef1ec0f80cadc223c13b06fa0ba231013ffdcd00710381e5c2fc7ebf175
+DIST regexp_parser-2.0.3.tar.gz 86862 BLAKE2B 261703b7f005d234bbb2be655b6f9974e9f160b36af9082339653f469b9a18cffd39e04878a0a007c09252be747928bcd04e59af1c5572bc3f627495432bcc3d SHA512 0df0c6a023b26c48570ec5761af4bc90ab78afeae4f6f6864529102b826301b11b8a2cbfa7dbdd4b18221be7450ccd0d69c603a4cdd800c0b68fd6e5cc3c0eff

diff --git a/dev-ruby/regexp_parser/regexp_parser-2.0.3.ebuild b/dev-ruby/regexp_parser/regexp_parser-2.0.3.ebuild
new file mode 100644
index 00000000000..f159a54f45d
--- /dev/null
+++ b/dev-ruby/regexp_parser/regexp_parser-2.0.3.ebuild
@@ -0,0 +1,37 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+USE_RUBY="ruby25 ruby26 ruby27"
+
+RUBY_FAKEGEM_TASK_TEST="test:full"
+
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
+
+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 ~sparc ~x86"
+IUSE=""
+
+DEPEND+=" =dev-util/ragel-6*"
+
+ruby_add_bdepend "dev-ruby/rake
+	test? ( 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
+}


             reply	other threads:[~2021-01-03  8:05 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03  8:05 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-09  7:18 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/regexp_parser/ 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
2022-03-18  6: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
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=1609661123.822348dc6d830fc32aca782ccf07d31a4a22b879.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