From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sshkit/
Date: Mon, 22 Oct 2018 06:02:09 +0000 (UTC) [thread overview]
Message-ID: <1540187259.4e697d7cf7b75053b3ef694cb6085026f561d7be.graaff@gentoo> (raw)
commit: 4e697d7cf7b75053b3ef694cb6085026f561d7be
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 22 05:47:39 2018 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Oct 22 05:47:39 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e697d7c
dev-ruby/sshkit: add 1.18.0
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11
dev-ruby/sshkit/Manifest | 1 +
dev-ruby/sshkit/sshkit-1.18.0.ebuild | 42 ++++++++++++++++++++++++++++++++++++
2 files changed, 43 insertions(+)
diff --git a/dev-ruby/sshkit/Manifest b/dev-ruby/sshkit/Manifest
index 539decd01a4..ceb1b9e62e0 100644
--- a/dev-ruby/sshkit/Manifest
+++ b/dev-ruby/sshkit/Manifest
@@ -1,2 +1,3 @@
DIST sshkit-1.16.1.gem 148480 BLAKE2B 4d33e5258a0a4fb9dd063bf914724d69bb838e6f5a461b1b6b355306e5a99f58021ddd9d8f5bc2074bbfdbab2a823132f491a4d3d76c86b2ee9c9156bef7223d SHA512 3866381a4a4c34ac29199f9eb295fb642af624f7e96971f2c752688a24e36787698a4817943317b1e6735afe0bb035e7d7e3d8b81b49022caed2ef20ee57ec57
DIST sshkit-1.17.0.gem 149504 BLAKE2B a44b00917eca7a4953f57821518b14b5a5ed4f8d70c9e2b728c22071c705e185da33b63845bffce6fcb2fc35ed8efa3bb3ba5202eb71edae52cfd99c26583874 SHA512 61f531651a76418e157c1affa55927e438ad3eda9dea2b3f0c26f566522df11d1d39eceef84f706aa7733b60c8428dbb3d7da863ada64a24c79567dc4a8c10ad
+DIST sshkit-1.18.0.gem 150016 BLAKE2B 3592bbacf2b9031ce9527f0ecfdcd0ec973239496c842fd659277498ec9a5d815ae77ff7b06afe7dd20d82577dab6ccfcbab79e7514752b41ddb1b80fcfed7cc SHA512 ceff9c7be99155b5e86e1564be221da5946b91b396ffc948aafbbc1a5214928020ee3db97615b780c91f4fefacff2174c4d0a33e54aa2e935552eecedac71bde
diff --git a/dev-ruby/sshkit/sshkit-1.18.0.ebuild b/dev-ruby/sshkit/sshkit-1.18.0.ebuild
new file mode 100644
index 00000000000..91c7106b40c
--- /dev/null
+++ b/dev-ruby/sshkit/sshkit-1.18.0.ebuild
@@ -0,0 +1,42 @@
+# Copyright 1999-2018 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+USE_RUBY="ruby23 ruby24 ruby25"
+
+# There are functional tests that require vagrant boxes to be set up.
+RUBY_FAKEGEM_TASK_TEST="test:units"
+
+RUBY_FAKEGEM_TASK_DOC=""
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md FAQ.md README.md"
+
+inherit ruby-fakegem
+
+DESCRIPTION="SSHKit makes it easy to write structured, testable SSH commands in Ruby"
+HOMEPAGE="https://github.com/capistrano/sshkit"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE=""
+
+ruby_add_rdepend "
+ >=dev-ruby/net-ssh-2.8.0:*
+ >=dev-ruby/net-scp-1.1.2
+"
+
+ruby_add_bdepend "test? ( dev-ruby/minitest dev-ruby/mocha )"
+
+all_ruby_prepare() {
+ sed -i -e '/bundler/I s:^:#:' Rakefile test/helper.rb || die
+ sed -i -e '/\(turn\|unindent\|reporters\)/I s:^:#:' \
+ -e '1irequire "set"; require "pathname"' test/helper.rb || die
+
+ # Fix assumption about parent directory name
+ sed -i -e '/assert_match/ s/sshkit/sshkit.*/' test/unit/test_deprecation_logger.rb || die
+}
+
+each_ruby_test() {
+ # Run tests directly to avoid dependencies in the Rakefile
+ ${RUBY} -Ilib:test:. -e "Dir['test/unit/**/test*.rb'].each{|f| require f}" || die
+}
next reply other threads:[~2018-10-22 6:02 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 6:02 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-14 18:41 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sshkit/ Sam James
2024-10-21 5:46 Hans de Graaff
2024-10-07 6:29 Hans de Graaff
2024-10-06 14:27 Sam James
2024-07-19 9:52 Hans de Graaff
2024-07-15 8:33 Hans de Graaff
2024-07-14 7:48 Hans de Graaff
2024-06-23 3:34 Hans de Graaff
2024-06-23 3:34 Hans de Graaff
2024-06-23 3:34 Hans de Graaff
2024-04-30 5:49 Hans de Graaff
2024-04-02 5:38 Hans de Graaff
2024-04-02 5:38 Hans de Graaff
2024-01-14 8:12 Hans de Graaff
2024-01-10 7:44 Hans de Graaff
2023-12-29 7:47 Hans de Graaff
2023-11-20 7:16 Hans de Graaff
2023-08-20 8:11 Sam James
2023-07-05 16:36 Hans de Graaff
2023-04-07 8:43 Sam James
2023-04-07 8:43 Sam James
2023-04-07 8:43 Sam James
2023-03-26 3:15 Sam James
2023-03-26 3:03 Sam James
2023-02-20 7:03 Hans de Graaff
2022-09-06 5:07 Hans de Graaff
2022-09-04 10:54 Hans de Graaff
2022-03-31 5:39 Hans de Graaff
2022-03-14 6:34 Hans de Graaff
2021-10-14 6:44 Hans de Graaff
2021-01-19 17:24 Hans de Graaff
2020-11-27 5:36 Hans de Graaff
2020-11-27 5:36 Hans de Graaff
2020-09-08 5:48 Hans de Graaff
2020-05-06 5:30 Hans de Graaff
2020-03-05 8:11 Hans de Graaff
2020-02-09 15:07 Hans de Graaff
2019-09-18 13:55 Hans de Graaff
2019-08-04 5:56 Hans de Graaff
2019-07-03 4:50 Hans de Graaff
2019-07-03 4:50 Hans de Graaff
2019-07-01 5:05 Hans de Graaff
2019-07-01 5:05 Hans de Graaff
2019-02-04 5:45 Hans de Graaff
2019-01-28 6:57 Hans de Graaff
2019-01-19 14:48 Hans de Graaff
2018-10-22 6:02 Hans de Graaff
2018-07-08 3:36 Hans de Graaff
2018-05-21 5:16 Hans de Graaff
2018-05-06 5:56 Hans de Graaff
2018-03-03 8:13 Hans de Graaff
2018-01-22 21:11 Hans de Graaff
2017-12-23 6:27 Hans de Graaff
2017-08-23 6:14 Hans de Graaff
2017-07-03 5:35 Hans de Graaff
2017-04-01 6:17 Hans de Graaff
2017-02-12 5:52 Hans de Graaff
2016-12-17 6:01 Hans de Graaff
2016-12-17 6:01 Hans de Graaff
2016-11-03 6:06 Hans de Graaff
2016-09-17 5:53 Hans de Graaff
2016-09-17 5:53 Hans de Graaff
2016-07-30 5:23 Hans de Graaff
2016-07-23 8:15 Hans de Graaff
2016-06-16 5:07 Hans de Graaff
2016-06-15 5:07 Hans de Graaff
2016-04-25 5:12 Hans de Graaff
2016-03-11 7:06 Hans de Graaff
2016-03-11 7:06 Hans de Graaff
2015-12-06 7:05 Hans de Graaff
2015-12-03 5:51 Hans de Graaff
2015-12-03 5:51 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=1540187259.4e697d7cf7b75053b3ef694cb6085026f561d7be.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