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/safe_yaml/
Date: Sun,  6 Sep 2020 06:48:45 +0000 (UTC)	[thread overview]
Message-ID: <1599374914.f50c19ea71c7bb8a1582934a96a518bac16c31e1.graaff@gentoo> (raw)

commit:     f50c19ea71c7bb8a1582934a96a518bac16c31e1
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Sep  6 06:42:56 2020 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Sep  6 06:48:34 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f50c19ea

dev-ruby/safe_yaml: add ruby27

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

 dev-ruby/safe_yaml/safe_yaml-1.0.5-r1.ebuild | 35 ++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)

diff --git a/dev-ruby/safe_yaml/safe_yaml-1.0.5-r1.ebuild b/dev-ruby/safe_yaml/safe_yaml-1.0.5-r1.ebuild
new file mode 100644
index 00000000000..ea0cd393ddd
--- /dev/null
+++ b/dev-ruby/safe_yaml/safe_yaml-1.0.5-r1.ebuild
@@ -0,0 +1,35 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+USE_RUBY="ruby25 ruby26 ruby27"
+
+RUBY_FAKEGEM_EXTRADOC="README.md"
+RUBY_FAKEGEM_RECIPE_TEST="none"
+
+inherit ruby-fakegem
+
+DESCRIPTION="Parse YAML safely, alternative implementation of YAML.load"
+HOMEPAGE="https://dtao.github.com/safe_yaml"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~sparc ~x86 ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+IUSE="test"
+
+ruby_add_bdepend "test? ( dev-ruby/hashie
+	dev-ruby/heredoc_unindent
+	dev-ruby/rspec:3 )"
+
+all_ruby_prepare() {
+	sed -i -e '/local timezone/askip "timezone"' spec/transform/to_date_spec.rb || die
+}
+
+each_ruby_test() {
+	# Run specs with monkeypatch
+	${RUBY} -S rspec-3 spec --tag ~libraries || die
+
+	# Running specs without monkeypatch
+	${RUBY} -S rspec-3 spec --tag libraries || die
+}


             reply	other threads:[~2020-09-06  6:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06  6:48 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-15  9:10 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/safe_yaml/ Hans de Graaff
2023-04-24 12:40 Sam James
2023-04-24 12:40 Sam James
2023-03-25  7:12 Sam James
2023-03-25  7:12 Sam James
2023-03-25  7:12 Sam James
2021-07-16  8:52 Hans de Graaff
2021-07-16  8:52 Hans de Graaff
2021-07-03  7:22 Hans de Graaff
2020-04-19 12:22 Sergei Trofimovich
2019-04-29  5:32 Hans de Graaff
2019-04-28 20:34 Thomas Deutschmann
2019-04-13 14:10 Mikle Kolyada
2019-04-13 12:27 Hans de Graaff
2019-02-23  7:16 Hans de Graaff
2019-01-28 21:45 Hans de Graaff
2018-05-21  5:16 Hans de Graaff
2017-08-24  5:49 Hans de Graaff
2017-08-24  5:49 Hans de Graaff
2017-07-06  4:56 Hans de Graaff
2017-07-06  4:56 Hans de Graaff
2016-12-09  6:59 Hans de Graaff
2016-10-12  4:53 Hans de Graaff
2016-07-21 19:38 Hans de Graaff
2016-06-13  4:37 Richard Farina
2016-03-06 18:45 Manuel Rüger
2016-03-06 18:45 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=1599374914.f50c19ea71c7bb8a1582934a96a518bac16c31e1.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