From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/ruby_engine/
Date: Mon, 18 Jul 2022 08:27:50 +0000 (UTC) [thread overview]
Message-ID: <1658132866.87cc49bc815afd414f2a19cea6619fdb916d4b07.graaff@gentoo> (raw)
commit: 87cc49bc815afd414f2a19cea6619fdb916d4b07
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 18 07:59:19 2022 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Jul 18 08:27:46 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=87cc49bc
dev-ruby/ruby_engine: new package, add 2.0.0
Dependency for forthcoming dev-ruby/rspec-pending_for.
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/ruby_engine/Manifest | 1 +
dev-ruby/ruby_engine/metadata.xml | 11 +++++++++++
dev-ruby/ruby_engine/ruby_engine-2.0.0.ebuild | 18 ++++++++++++++++++
3 files changed, 30 insertions(+)
diff --git a/dev-ruby/ruby_engine/Manifest b/dev-ruby/ruby_engine/Manifest
new file mode 100644
index 000000000000..da5ec0bb4a4c
--- /dev/null
+++ b/dev-ruby/ruby_engine/Manifest
@@ -0,0 +1 @@
+DIST ruby_engine-2.0.0.gem 21504 BLAKE2B b931969150735aa30fe910ad5e9861853180cb4247a803149e91b302fef0e7b48ccddf7316d855cbb23e8cc0d1e1b6cdb598b9bf6ed3e973090221b096184f28 SHA512 de1363617c57caa813f1526b71c9119f5f29e49b86e11476299e56234c585d9cbb594a7c5383fed988abfc1b5ec13d2005a96d96f6671bfdf316fa6836fba9de
diff --git a/dev-ruby/ruby_engine/metadata.xml b/dev-ruby/ruby_engine/metadata.xml
new file mode 100644
index 000000000000..9f2b7707c89e
--- /dev/null
+++ b/dev-ruby/ruby_engine/metadata.xml
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="project">
+ <email>ruby@gentoo.org</email>
+ <name>Gentoo Ruby Project</name>
+ </maintainer>
+ <upstream>
+ <remote-id type="github">janlelis/ruby_engine</remote-id>
+ </upstream>
+</pkgmetadata>
diff --git a/dev-ruby/ruby_engine/ruby_engine-2.0.0.ebuild b/dev-ruby/ruby_engine/ruby_engine-2.0.0.ebuild
new file mode 100644
index 000000000000..17da59c4d792
--- /dev/null
+++ b/dev-ruby/ruby_engine/ruby_engine-2.0.0.ebuild
@@ -0,0 +1,18 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+USE_RUBY="ruby27 ruby30 ruby31"
+
+RUBY_FAKEGEM_EXTRADOC="ChangeLog.md README.rdoc"
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+inherit ruby-fakegem
+
+DESCRIPTION="Gives you an RubyEngine class that simplifies checking for your Ruby implementation"
+HOMEPAGE="https://github.com/janlelis/ruby_version"
+
+LICENSE="MIT"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64"
+IUSE=""
next reply other threads:[~2022-07-18 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 8:27 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-19 6:07 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/ruby_engine/ Hans de Graaff
2022-07-20 17:01 Sam James
2022-07-20 17:01 Sam James
2022-12-05 19:54 Arthur Zamarin
2023-03-26 6:44 Hans de Graaff
2023-07-11 8:13 Jakov Smolić
2023-12-31 10:29 Hans de Graaff
2024-04-04 6:06 Hans de Graaff
2024-04-27 7:43 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=1658132866.87cc49bc815afd414f2a19cea6619fdb916d4b07.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