From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-cache/
Date: Thu, 7 Nov 2019 07:51:14 +0000 (UTC) [thread overview]
Message-ID: <1573113068.1ad0cb5d0e401c5f51d4dbde2415e4bfae03ea2b.graaff@gentoo> (raw)
commit: 1ad0cb5d0e401c5f51d4dbde2415e4bfae03ea2b
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 7 06:02:16 2019 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Nov 7 07:51:08 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ad0cb5d
dev-ruby/rack-cache: cleanup
Package-Manager: Portage-2.3.76, Repoman-2.3.16
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/rack-cache/Manifest | 1 -
dev-ruby/rack-cache/rack-cache-1.8.0.ebuild | 40 -----------------------------
2 files changed, 41 deletions(-)
diff --git a/dev-ruby/rack-cache/Manifest b/dev-ruby/rack-cache/Manifest
index b265f706d62..8a0f8b5707b 100644
--- a/dev-ruby/rack-cache/Manifest
+++ b/dev-ruby/rack-cache/Manifest
@@ -1,2 +1 @@
-DIST rack-cache-1.8.0.tar.gz 260732 BLAKE2B 79104b2dd82ec1a95abbe84a97e8a7cea918f87e3845816d6252610ed24e82c4bb38fa7dc34ddea9517af06d21091c23b5316ce87a9f80d49fcd3be1a7764b22 SHA512 b5235c0b3d2a3476555bb2420bc5d69ae12d8d650fb9ea1d8d8fd4f1dff0c45f47e920c58c1e44d1e565eb45248d4e63e7643c8c50d43706365a36ae80f2eec8
DIST rack-cache-1.9.0.tar.gz 260825 BLAKE2B 58f3bfbf6af9c515ef1dc7406c6b41ba8ce37c3cc9533a21f0480565fa72b72acb517a161a7d00bfd21e1e2b2379ab85796e507fe478c601c287031a70858bff SHA512 da998796a26338af2a484a8bb87f152706f33de719cc546f7bd4c4222ca5c52297d0b4dbe233e4362d6b5e6fedb7b527ce9a29cc03a6fbeee12e760afc070a93
diff --git a/dev-ruby/rack-cache/rack-cache-1.8.0.ebuild b/dev-ruby/rack-cache/rack-cache-1.8.0.ebuild
deleted file mode 100644
index c377e43b3b2..00000000000
--- a/dev-ruby/rack-cache/rack-cache-1.8.0.ebuild
+++ /dev/null
@@ -1,40 +0,0 @@
-# Copyright 1999-2019 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-USE_RUBY="ruby23 ruby24 ruby25 ruby26"
-
-# no documentation is generable, it needs hanna, which is broken
-RUBY_FAKEGEM_RECIPE_DOC="none"
-
-RUBY_FAKEGEM_TASK_TEST="none"
-
-RUBY_FAKEGEM_EXTRADOC="CHANGES README.md doc/*"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Enable HTTP caching for Rack-based applications that produce freshness info"
-HOMEPAGE="https://github.com/rtomayko/rack-cache"
-SRC_URI="https://github.com/rtomayko/rack-cache/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="MIT"
-SLOT="1.2"
-KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
-IUSE=""
-
-ruby_add_rdepend "dev-ruby/rack:*"
-
-ruby_add_bdepend "test? (
- dev-ruby/maxitest
- >=dev-ruby/minitest-5.7.0:5
- >=dev-ruby/mocha-0.13.0 )"
-
-all_ruby_prepare() {
- sed -i -e '/bundler/ s:^:#:' \
- -e "2i require 'timeout'" \
- test/test_helper.rb || die
-}
-
-each_ruby_test() {
- ${RUBY} -I.:lib:test -e 'Dir["test/*_test.rb"].each{|f| require f}' || die
-}
next reply other threads:[~2019-11-07 7:51 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 7:51 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 11:11 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-cache/ Sam James
2024-04-06 6:16 Hans de Graaff
2024-04-06 6:16 Hans de Graaff
2024-03-08 8:09 Hans de Graaff
2024-03-02 6:27 Hans de Graaff
2024-03-02 6:27 Hans de Graaff
2023-12-12 7:11 Hans de Graaff
2023-12-08 6:56 Hans de Graaff
2023-12-08 6:56 Hans de Graaff
2023-08-29 16:53 Hans de Graaff
2023-07-19 5:26 Hans de Graaff
2023-07-11 4:37 Hans de Graaff
2023-04-03 3:03 Sam James
2022-12-24 15:00 Hans de Graaff
2022-04-23 5:14 Hans de Graaff
2022-03-25 10:22 Hans de Graaff
2022-03-25 10:22 Hans de Graaff
2022-03-23 6:42 Hans de Graaff
2021-11-08 2:51 Yixun Lan
2021-09-27 5:14 Hans de Graaff
2021-09-27 5:14 Hans de Graaff
2020-10-23 5:09 Hans de Graaff
2020-09-11 5:14 Hans de Graaff
2020-07-26 15:12 Hans de Graaff
2020-07-26 15:12 Hans de Graaff
2020-06-14 6:28 Hans de Graaff
2020-06-14 6:28 Hans de Graaff
2020-04-25 12:16 Hans de Graaff
2020-04-22 17:07 Sergei Trofimovich
2020-04-22 17:07 Sergei Trofimovich
2020-04-22 17:07 Sergei Trofimovich
2020-04-22 17:07 Sergei Trofimovich
2020-04-09 4:13 Hans de Graaff
2020-01-09 5:51 Hans de Graaff
2019-11-07 7:51 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2019-02-27 6:10 Hans de Graaff
2019-02-27 6:10 Hans de Graaff
2019-01-27 19:13 Hans de Graaff
2018-06-08 5:33 Hans de Graaff
2018-05-15 5:15 Hans de Graaff
2018-02-25 22:01 Sergei Trofimovich
2018-01-13 8:46 Hans de Graaff
2018-01-13 8:46 Hans de Graaff
2017-09-07 5:36 Hans de Graaff
2017-07-02 5:43 Hans de Graaff
2017-01-24 6:06 Hans de Graaff
2017-01-24 6:06 Hans de Graaff
2016-07-15 5:38 Hans de Graaff
2016-03-21 22:09 Manuel RĂ¼ger
2016-02-12 6:20 Hans de Graaff
2016-02-03 7:02 Hans de Graaff
2016-01-20 13:42 Fabian Groffen
2016-01-02 8:26 Hans de Graaff
2016-01-02 8:26 Hans de Graaff
2016-01-02 8:26 Hans de Graaff
2015-11-21 15:45 Markus Meier
2015-11-16 5:55 Jeroen Roovers
2015-11-15 8:14 Hans de Graaff
2015-11-15 7:22 Hans de Graaff
2015-10-08 8:13 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=1573113068.1ad0cb5d0e401c5f51d4dbde2415e4bfae03ea2b.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