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-util/cucumber-rails/
Date: Wed, 13 Nov 2024 06:45:34 +0000 (UTC)	[thread overview]
Message-ID: <1731480311.1f44bfce460691d1eed82dac96e755852486a97c.graaff@gentoo> (raw)

commit:     1f44bfce460691d1eed82dac96e755852486a97c
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 13 06:45:11 2024 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Nov 13 06:45:11 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f44bfce

dev-util/cucumber-rails: add 3.0.1

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-util/cucumber-rails/Manifest                   |  1 +
 .../cucumber-rails/cucumber-rails-3.0.1.ebuild     | 48 ++++++++++++++++++++++
 2 files changed, 49 insertions(+)

diff --git a/dev-util/cucumber-rails/Manifest b/dev-util/cucumber-rails/Manifest
index ed55fc51accb..433e69e3c422 100644
--- a/dev-util/cucumber-rails/Manifest
+++ b/dev-util/cucumber-rails/Manifest
@@ -1,2 +1,3 @@
 DIST cucumber-rails-2.6.1.tar.gz 43079 BLAKE2B c45211c8a2375fc2b488d22fb74041e5dcf56027d6644721b5023b8ad9e68f07593c448acb88b7c0e51dcad7da0213d48726e20175ecd5fd04f16174e44b848a SHA512 dd2ed4afecf74e8aac0fa360d81a27407df999b041b21c597e9ac141422cb0ece89eaa74d8da9a4fc2858efaf242837d8237a9ceee44875cff2c50d288fad480
 DIST cucumber-rails-3.0.0.tar.gz 37102 BLAKE2B 095b867916ccaf4ac30b6140045700002c0a83e16c86162c4891cfa21a74b2d4f2f05646f533e2b618d5c99ee74344d68042d2e47edfa6e0adfc35aa1ed31721 SHA512 66c045026b13dc94198e4095d41b8ca4bbde345f221443b834f020173b7b0bb82e5db3880691ad8adea7e39fd0ab6e987a97347712b7a0a9697825a151206beb
+DIST cucumber-rails-3.0.1.tar.gz 37596 BLAKE2B 37c861b361dd0e7aefcd1be4bd66cf10eb875ea652767e7113c3b9caf2fac5a874a9ec5624490e812412b2c69ea00975f85b40e2cee1c0c0d2f005c30941f49d SHA512 b9ba7aec5d76085c36f60786a37cc0f8c04866965e1785ba194795212a5923680aee3a2c7b38825e8cff354e2ef87dc209c66e19dccf0cb78745b0db06567134

diff --git a/dev-util/cucumber-rails/cucumber-rails-3.0.1.ebuild b/dev-util/cucumber-rails/cucumber-rails-3.0.1.ebuild
new file mode 100644
index 000000000000..2e7c94c18ea5
--- /dev/null
+++ b/dev-util/cucumber-rails/cucumber-rails-3.0.1.ebuild
@@ -0,0 +1,48 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+USE_RUBY="ruby31 ruby32 ruby33"
+
+# There are also cucumber features. They require a Rails project with
+# factory girl which we don't have packaged yet.
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
+
+RUBY_FAKEGEM_GEMSPEC="cucumber-rails.gemspec"
+
+RUBY_FAKEGEM_BINWRAP=""
+
+inherit ruby-fakegem
+
+DESCRIPTION="Executable feature scenarios for Rails"
+HOMEPAGE="https://cucumber.io/"
+SRC_URI="https://github.com/cucumber/cucumber-rails/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+LICENSE="Ruby"
+
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64"
+IUSE="test"
+
+# Restrict tests since Appraisal is now mandatory to manage different
+# rails versions, even for the specs.
+RESTRICT="test"
+#ruby_add_bdepend "
+#	test? (
+#		>=dev-ruby/ammeter-0.2.2
+#		>=dev-ruby/rspec-rails-2.7.0:2
+#	)"
+
+ruby_add_rdepend "
+	>=dev-ruby/capybara-3.11:3
+	>=dev-util/cucumber-5 <dev-util/cucumber-10
+	>=dev-ruby/rails-5.2:* <dev-ruby/rails-8:*
+"
+
+all_ruby_prepare() {
+	rm Gemfile || die
+	sed -i -e '/[Bb]undler/d' Rakefile || die
+	sed -e 's/__dir__/"."/' \
+		-i ${RUBY_FAKEGEM_GEMSPEC} || die
+}


             reply	other threads:[~2024-11-13  6:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  6:45 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-01  6:27 [gentoo-commits] repo/gentoo:master commit in: dev-util/cucumber-rails/ Hans de Graaff
2024-12-01  8:09 Hans de Graaff
2024-08-06  5:51 Hans de Graaff
2023-11-03  7:57 Hans de Graaff
2023-11-03  7:57 Hans de Graaff
2023-07-08 14:09 Hans de Graaff
2023-04-10 10:57 Hans de Graaff
2023-04-10 10:57 Hans de Graaff
2022-12-07 18:24 Hans de Graaff
2022-10-17  5:25 Hans de Graaff
2022-10-09  7:22 Hans de Graaff
2022-07-19  6:14 Hans de Graaff
2022-06-26  5:43 Hans de Graaff
2022-04-09 12:08 Hans de Graaff
2022-04-07  5:46 Hans de Graaff
2022-04-07  5:46 Hans de Graaff
2022-03-15 16:01 Hans de Graaff
2022-03-15  6:59 Hans de Graaff
2021-08-15  7:41 Hans de Graaff
2021-07-22  4:45 Hans de Graaff
2021-07-14  9:20 Hans de Graaff
2021-07-09  6:55 Hans de Graaff
2021-07-06  8:37 Hans de Graaff
2021-07-06  8:37 Hans de Graaff
2020-10-13  4:14 Hans de Graaff
2020-06-27  8:11 Hans de Graaff
2020-03-14 14:37 Hans de Graaff
2020-03-14 14:37 Hans de Graaff
2020-03-09  6:32 Hans de Graaff
2019-11-03  9:28 Hans de Graaff
2019-08-15  5:12 Hans de Graaff
2019-05-04  9:23 Hans de Graaff
2019-04-28  5:55 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2018-06-04  9:56 Hans de Graaff
2018-04-09  4:32 Hans de Graaff
2018-01-22 20:48 Hans de Graaff
2017-05-20  5:53 Hans de Graaff
2017-05-20  5:53 Hans de Graaff
2016-09-30  5:46 Hans de Graaff
2016-08-10  5:30 Hans de Graaff
2016-08-10  5:30 Hans de Graaff
2016-04-10  0:28 Manuel Rüger
2016-03-02  6:09 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=1731480311.1f44bfce460691d1eed82dac96e755852486a97c.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