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: Fri,  2 Oct 2020 05:15:58 +0000 (UTC)	[thread overview]
Message-ID: <1601615747.f0d2423a7e8bdc8b82e321d46a550102b355f02a.graaff@gentoo> (raw)

commit:     f0d2423a7e8bdc8b82e321d46a550102b355f02a
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Oct  2 05:15:47 2020 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Oct  2 05:15:47 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f0d2423a

dev-ruby/regexp_parser: add 1.8.1

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

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

diff --git a/dev-ruby/regexp_parser/Manifest b/dev-ruby/regexp_parser/Manifest
index 2af280b03dc..6980112fd2c 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.5.1.tar.gz 82482 BLAKE2B ff1746e52e786e273923dd222ea8c8276eb1e4ffe9bf899068160dec229784709ba679983c1e43736c128ec094861174bd43e0aceea704ee2d38aff4a53e6775 SHA512 4856fbcac800083b417880c30b5d6a5ea445bb85950bdd7898f368bfa2d44b01b1e2058b279f1640cf1cf4d7b28e225d25bc2d356d2c4a7c1be0a2c621dd3827
 DIST regexp_parser-1.7.1.tar.gz 83865 BLAKE2B 1aab4f5c4d399ee48951a9fa9f24fef14073ca5267ec29e5011880274d2749a7a3d1f5cb2a6a5107d5c848537367e1f725a6de9bb9af8803ccc8ccedaac415eb SHA512 fda810bc18039484725df5c6092b3d1b31f398e337cbace253cfdfa934274902f2dcb4e64c4fd0bb24379c79ea2976383313c1a5cd4ad246ecb7eabfd1a47d64
 DIST regexp_parser-1.8.0.tar.gz 85071 BLAKE2B 1d9f60617372f872e8b372bbee0f808d060add768094d53bc05ef2f4757936fcfb4772dc0a2ba59630884b339a3c66d34336cfa05825f4ef53427ddd3528b9d7 SHA512 bbf2429c00c214288869b77641e44d04591c3917ceeb9262ae8638c0731b020bead4a7b11d397ef2e1a26752c660addcc46fd94a4e557766d230de71b99a9501
+DIST regexp_parser-1.8.1.tar.gz 85379 BLAKE2B 341f16b6fce9654984c9fbab589ef0991d50f42e935558da2741e2dcbfe8cbc21200fd2233abff2907a1bd44c5b350b41a665ef4f993591b92f31d3280a24ba5 SHA512 6642dad18313e10856d86bf3ecd2fc5b0927698ca8e37f17745b755088f750febf2c05fd098e99b87543cd90f944ae0d9c4c03452048d2b44b4b1fb68e986045

diff --git a/dev-ruby/regexp_parser/regexp_parser-1.8.1.ebuild b/dev-ruby/regexp_parser/regexp_parser-1.8.1.ebuild
new file mode 100644
index 00000000000..9a339fd368c
--- /dev/null
+++ b/dev-ruby/regexp_parser/regexp_parser-1.8.1.ebuild
@@ -0,0 +1,37 @@
+# Copyright 1999-2020 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="1"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~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:[~2020-10-02  5:16 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  5:15 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
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-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=1601615747.f0d2423a7e8bdc8b82e321d46a550102b355f02a.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