From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/climate_control/
Date: Fri, 31 Mar 2023 01:03:50 +0000 (UTC) [thread overview]
Message-ID: <1680224101.19767077b799d70025e5876cf1b6b4496f718d6f.sam@gentoo> (raw)
commit: 19767077b799d70025e5876cf1b6b4496f718d6f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 31 00:48:57 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 31 00:55:01 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=19767077
dev-ruby/climate_control: drop 1.0.1
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/climate_control/Manifest | 1 -
.../climate_control/climate_control-1.0.1.ebuild | 29 ----------------------
2 files changed, 30 deletions(-)
diff --git a/dev-ruby/climate_control/Manifest b/dev-ruby/climate_control/Manifest
index 331ee6405b9a..3c146a2391ba 100644
--- a/dev-ruby/climate_control/Manifest
+++ b/dev-ruby/climate_control/Manifest
@@ -1,2 +1 @@
-DIST climate_control-1.0.1.gem 9728 BLAKE2B f2d267e86c58fdbb7a85508f56a091166809d108c2e66702df50962086a89a134e6a47a1e53c36272c563f1d4a0225fc613490616d67fbe04e9647b7fe8cfda6 SHA512 2dfd790b444409275571881d19c3712c6542890499f3d55e5f8ea3775166c01adbb216a0749b0c4e126d631cba690c0edc3f8c49143fc0ff3bcc8b25545bf218
DIST climate_control-1.2.0.gem 10752 BLAKE2B 5c7c1d0b1ec50f12139e47a0c0f2d5753c6165aa96bb995be12f65cef4a222fc4fa96b66e8c475b3ebe2f353c335a6667e12a9a2a8a869331a1f41f72d686d94 SHA512 282f40d5d9d7b4a6577ea13dd92141c985a0c1bd7d6688cb2bca2529721a0523a1e9ac4ba1c6a27a43b286ac664e502698ef2c0578a9030283a4b18f7cb0a5e8
diff --git a/dev-ruby/climate_control/climate_control-1.0.1.ebuild b/dev-ruby/climate_control/climate_control-1.0.1.ebuild
deleted file mode 100644
index afca40f5eb3b..000000000000
--- a/dev-ruby/climate_control/climate_control-1.0.1.ebuild
+++ /dev/null
@@ -1,29 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-USE_RUBY="ruby26 ruby27 ruby30 ruby31"
-
-RUBY_FAKEGEM_TASK_DOC=""
-RUBY_FAKEGEM_EXTRADOC="NEWS README.md"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Easily manage your environment"
-HOMEPAGE="https://github.com/thoughtbot/climate_control"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE=""
-
-all_ruby_prepare() {
- # Avoid dependencies on simplecov and git.
- sed -i -e '/simplecov/I s:^:#:' spec/spec_helper.rb || die
- sed -i -e 's/git ls-files/find * -print/' ${RUBY_FAKEGEM_GEMSPEC} || die
-}
next reply other threads:[~2023-03-31 1:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 1:03 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-01 8:38 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/climate_control/ Hans de Graaff
2023-12-31 19:49 Hans de Graaff
2023-07-12 7:46 Hans de Graaff
2022-12-27 6:56 Hans de Graaff
2022-12-07 17:57 Hans de Graaff
2022-05-07 6:33 Hans de Graaff
2020-08-22 7:56 Hans de Graaff
2018-06-26 16:02 Hans de Graaff
2018-02-02 16:44 Hans de Graaff
2017-05-14 5:40 Hans de Graaff
2017-01-08 6:43 Hans de Graaff
2016-07-24 14:47 Hans de Graaff
2016-03-13 13:36 Manuel Rüger
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=1680224101.19767077b799d70025e5876cf1b6b4496f718d6f.sam@gentoo \
--to=sam@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