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/recog/
Date: Sun, 17 Nov 2019 07:36:31 +0000 (UTC)	[thread overview]
Message-ID: <1573976184.c644c998d25d37b0a0c91f3da7646af905f9d850.graaff@gentoo> (raw)

commit:     c644c998d25d37b0a0c91f3da7646af905f9d850
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 17 06:41:15 2019 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Nov 17 07:36:24 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c644c998

dev-ruby/recog: cleanup

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

 dev-ruby/recog/Manifest            |  1 -
 dev-ruby/recog/recog-2.1.46.ebuild | 39 --------------------------------------
 2 files changed, 40 deletions(-)

diff --git a/dev-ruby/recog/Manifest b/dev-ruby/recog/Manifest
index c16e6f6f6fc..c9def2fb70e 100644
--- a/dev-ruby/recog/Manifest
+++ b/dev-ruby/recog/Manifest
@@ -1,4 +1,3 @@
-DIST recog-2.1.46.gem 246784 BLAKE2B 1b151fb6944371d186154ecc28eb74f6727b92394bf3686fb7230603e64a37438dc63293929b63025794ae053304ced7f74da4d530d24f77a6274ffe69cfff7d SHA512 aae48fc9a91e7f750944a97e562789efde14474b42d063dcb2dacd038e78fd20222719e0f17d66c8a13b7261e2e58567bad4db0a84893724a5c04504d35efbc0
 DIST recog-2.3.2.gem 259584 BLAKE2B 035cdcb23fa837798fd256d00eb3cfa11b6ebeefd218c3c00a0f68ad1311efc6ce62a3db537cdc7a692d77e10b45c63f7c391314b05ca93c9afc269e67e7ba24 SHA512 0deb0e2354bab3ae190b0b71d370755de802d679a37a2d907fcc6503a12120e27d607bd3f31db62f678e4488228977132f3816a4586e5e85ba37f7ff6cd27733
 DIST recog-2.3.4.gem 262656 BLAKE2B ca2ea05844f5fde74859b22a9f710e5a9f0d44d789d49fb2c8502f4f09f5e5a3772d4a4187e5f0c10ec250c84599defc9dc86dd5602a7bdc7586f07ed14df350 SHA512 4ebf2ce4d502eb103eb3d10b7c01f3e43a402b90d8883f76cedb93edea32f31d196c4141c11264739f73ee9afe8590c50a368897a1286ff408d4454e89622be6
 DIST recog-2.3.5.gem 263168 BLAKE2B da850cc08e7ffebd34e040eac15ecc62ab857c61d8a65cf5e9889f94c0173204ef8de5c712c89ddfc67c9d6bb8c01c09c702547de1bbdd7b12d121e4f4fefe7b SHA512 a45bc81c17edc9e431aa945678c77c573e2d1ad2352b4b4862492108cda0620145f6dc04a7d7ff2a6b456db32ed0348af4e61cd2be187f9d3de2b421f1f4e4ce

diff --git a/dev-ruby/recog/recog-2.1.46.ebuild b/dev-ruby/recog/recog-2.1.46.ebuild
deleted file mode 100644
index 1f8f71315a9..00000000000
--- a/dev-ruby/recog/recog-2.1.46.ebuild
+++ /dev/null
@@ -1,39 +0,0 @@
-# Copyright 1999-2019 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-USE_RUBY="ruby24 ruby25"
-RUBY_FAKEGEM_BINWRAP=""
-RUBY_FAKEGEM_RECIPE_DOC="rdoc"
-RUBY_FAKEGEM_EXTRADOC="README.md"
-
-RUBY_FAKEGEM_EXTRAINSTALL="xml"
-
-inherit ruby-fakegem eapi7-ver
-
-DESCRIPTION="Pattern recognition for hosts, services, and content"
-HOMEPAGE="https://github.com/rapid7/recog"
-
-LICENSE="BSD-2"
-SLOT="$(ver_cut 1)"
-KEYWORDS="~amd64 ~arm ~x86"
-IUSE=""
-
-ruby_add_rdepend "dev-ruby/nokogiri
-		!<dev-ruby/recog-2.0.6-r1"
-
-ruby_add_bdepend "test? (
-	dev-ruby/regexp_parser:0
-	dev-ruby/rspec:3
-	dev-util/aruba
-	dev-util/cucumber
-)"
-
-all_ruby_prepare() {
-	sed -i -e '/simplecov/I s:^:#:' -e '1igem "regexp_parser", "~>0.2"' spec/spec_helper.rb || die
-}
-
-each_ruby_test() {
-	RSPEC_VERSION=3 ruby-ng_rspec
-	ruby-ng_cucumber
-}


             reply	other threads:[~2019-11-17  7:36 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17  7:36 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-13  6:41 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/recog/ Hans de Graaff
2025-08-27  5:26 Hans de Graaff
2025-08-10  8:40 Hans de Graaff
2025-07-18  5:06 Hans de Graaff
2025-07-17  8:01 Hans de Graaff
2025-06-10  4:56 Hans de Graaff
2025-06-02 10:48 Hans de Graaff
2025-03-26  6:57 Hans de Graaff
2025-03-21 10:50 Hans de Graaff
2025-03-21 10:50 Hans de Graaff
2025-03-08 16:49 Hans de Graaff
2025-02-03  6:43 Hans de Graaff
2025-01-23  5:57 Hans de Graaff
2025-01-23  5:57 Hans de Graaff
2024-10-05  7:00 Hans de Graaff
2024-08-20  5:26 Hans de Graaff
2024-07-22  5:16 Hans de Graaff
2024-07-22  5:16 Hans de Graaff
2024-07-22  5:16 Hans de Graaff
2024-06-21 11:21 Hans de Graaff
2024-04-13  6:24 Hans de Graaff
2024-04-13  6:24 Hans de Graaff
2024-03-04 18:33 Rick Farina
2023-12-21  6:48 Hans de Graaff
2023-12-20  7:13 Hans de Graaff
2023-08-29 14:50 Hans de Graaff
2023-08-29 14:50 Hans de Graaff
2023-08-27  6:11 Hans de Graaff
2023-07-10 19:08 Hans de Graaff
2023-04-27 11:25 Hans de Graaff
2023-03-19  7:14 Hans de Graaff
2023-03-19  7:14 Hans de Graaff
2022-10-28  7:05 Hans de Graaff
2022-10-28  7:05 Hans de Graaff
2022-08-27  6:18 Hans de Graaff
2022-07-01 12:57 Hans de Graaff
2022-04-23  8:01 Hans de Graaff
2021-06-20  6:03 Hans de Graaff
2021-06-20  6:03 Hans de Graaff
2021-02-19  6:47 Hans de Graaff
2021-01-03  8:05 Hans de Graaff
2021-01-03  8:05 Hans de Graaff
2020-10-23  5:09 Hans de Graaff
2020-09-11  4:06 Hans de Graaff
2020-08-22  7:56 Hans de Graaff
2020-07-12  6:35 Hans de Graaff
2020-03-06  7:10 Hans de Graaff
2019-11-16  6:42 Hans de Graaff
2019-10-27  5:23 Hans de Graaff
2019-10-24  5:41 Hans de Graaff
2019-10-13  6:38 Hans de Graaff
2019-05-23  5:39 Hans de Graaff
2019-04-13  6:34 Hans de Graaff
2019-04-13  6:34 Hans de Graaff
2018-11-21 18:21 Rick Farina
2018-02-24  8:49 Hans de Graaff
2018-02-08 19:01 Hans de Graaff
2017-08-19  7:11 Hans de Graaff
2017-05-09  3:09 Richard Farina
2017-04-21  5:07 Hans de Graaff
2016-04-17 10:38 Manuel Rüger
2015-12-24 15:50 Manuel Rüger
2015-10-08 20:38 Richard Farina
2015-10-08 19:27 Richard Farina
2015-10-01  6:07 Hans de Graaff
2015-09-22  5:18 Hans de Graaff
2015-09-07 21:56 Richard Farina
2015-09-05  6:10 Hans de Graaff
2015-09-05  6:06 Hans de Graaff
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=1573976184.c644c998d25d37b0a0c91f3da7646af905f9d850.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