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: Sat, 14 Mar 2020 14:37:43 +0000 (UTC)	[thread overview]
Message-ID: <1584196647.2ededcc3f1cbb88559a1cbfbd857eaa9ac0feb18.graaff@gentoo> (raw)

commit:     2ededcc3f1cbb88559a1cbfbd857eaa9ac0feb18
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 14 14:37:01 2020 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Mar 14 14:37:27 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2ededcc3

dev-util/cucumber-rails: avoid unneeded binstubs

Closes: https://bugs.gentoo.org/711996
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 .../{cucumber-rails-2.0.0.ebuild => cucumber-rails-2.0.0-r1.ebuild}     | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev-util/cucumber-rails/cucumber-rails-2.0.0.ebuild b/dev-util/cucumber-rails/cucumber-rails-2.0.0-r1.ebuild
similarity index 97%
rename from dev-util/cucumber-rails/cucumber-rails-2.0.0.ebuild
rename to dev-util/cucumber-rails/cucumber-rails-2.0.0-r1.ebuild
index b66d33c4183..8b941d88443 100644
--- a/dev-util/cucumber-rails/cucumber-rails-2.0.0.ebuild
+++ b/dev-util/cucumber-rails/cucumber-rails-2.0.0-r1.ebuild
@@ -12,6 +12,8 @@ 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"


             reply	other threads:[~2020-03-14 14:37 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 14:37 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-11-13  6:45 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-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=1584196647.2ededcc3f1cbb88559a1cbfbd857eaa9ac0feb18.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