From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/ruby-ssl/
Date: Mon, 19 Mar 2018 06:21:56 +0000 (UTC) [thread overview]
Message-ID: <1521440497.e562724c27361ef85ee184f744fc8bcd9adc159f.graaff@gentoo> (raw)
commit: e562724c27361ef85ee184f744fc8bcd9adc159f
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 19 06:04:05 2018 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Mar 19 06:21:37 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e562724c
virtual/ruby-ssl: add ruby25 version
Package-Manager: Portage-2.3.24, Repoman-2.3.6
virtual/ruby-ssl/ruby-ssl-10.ebuild | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/virtual/ruby-ssl/ruby-ssl-10.ebuild b/virtual/ruby-ssl/ruby-ssl-10.ebuild
new file mode 100644
index 00000000000..9efd56b247a
--- /dev/null
+++ b/virtual/ruby-ssl/ruby-ssl-10.ebuild
@@ -0,0 +1,26 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+USE_RUBY="ruby22 ruby23 ruby24 ruby25"
+
+inherit ruby-ng
+
+DESCRIPTION="Virtual ebuild for the Ruby OpenSSL bindings"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+
+RDEPEND="
+ ruby_targets_ruby22? ( dev-lang/ruby:2.2[ssl] )
+ ruby_targets_ruby23? ( dev-lang/ruby:2.3[ssl] )
+ ruby_targets_ruby24? ( dev-lang/ruby:2.4[ssl] )
+ ruby_targets_ruby25? ( dev-lang/ruby:2.5[ssl] )
+"
+
+pkg_setup() { :; }
+src_unpack() { :; }
+src_prepare() { :; }
+src_compile() { :; }
+src_install() { :; }
+pkg_preinst() { :; }
+pkg_postinst() { :; }
next reply other threads:[~2018-03-19 6:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 6:21 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-17 4:38 [gentoo-commits] repo/gentoo:master commit in: virtual/ruby-ssl/ Viorel Munteanu
2024-04-01 8:47 Hans de Graaff
2023-09-23 7:07 Hans de Graaff
2023-06-23 9:38 Sam James
2023-05-15 9:10 Hans de Graaff
2023-04-10 11:04 Hans de Graaff
2022-08-27 7:53 Sam James
2022-05-08 16:12 WANG Xuerui
2022-03-12 7:21 Hans de Graaff
2021-09-12 7:56 Hans de Graaff
2021-07-21 10:27 Marek Szuba
2021-05-13 15:19 David Seifert
2021-01-06 12:42 Fabian Groffen
2020-12-28 7:46 Hans de Graaff
2020-12-27 19:00 Fabian Groffen
2020-12-20 5:15 Sam James
2020-08-07 7:46 Hans de Graaff
2020-01-16 6:52 Hans de Graaff
2019-11-17 7:36 Hans de Graaff
2019-08-21 16:28 Hans de Graaff
2019-04-09 5:53 Hans de Graaff
2019-03-30 19:50 Mikle Kolyada
2019-01-09 8:07 Hans de Graaff
2018-04-27 7:09 Hans de Graaff
2018-04-13 8:04 Hans de Graaff
2018-04-13 8:04 Hans de Graaff
2018-04-13 8:04 Hans de Graaff
2018-03-20 6:07 Hans de Graaff
2017-11-30 20:06 Sergei Trofimovich
2017-06-30 11:17 Alexis Ballier
2017-05-15 13:28 Michał Górny
2017-01-27 6:32 Hans de Graaff
2016-12-16 21:06 Hans de Graaff
2016-12-16 21:06 Hans de Graaff
2015-12-31 8:29 Hans de Graaff
2015-12-31 8:29 Hans de Graaff
2015-09-29 5:36 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=1521440497.e562724c27361ef85ee184f744fc8bcd9adc159f.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