From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sigdump/
Date: Wed, 4 Apr 2018 19:41:30 +0000 (UTC) [thread overview]
Message-ID: <1522870879.b58d806f665d02ccfd774315584e902492f29875.graaff@gentoo> (raw)
commit: b58d806f665d02ccfd774315584e902492f29875
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 4 19:40:55 2018 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Apr 4 19:41:19 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b58d806f
dev-ruby/sigdump: initial import of 0.2.4
Dependency for forthcoming app-admin/fluentd, bug 652434
Moved from "graaff" overlay.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
dev-ruby/sigdump/Manifest | 1 +
dev-ruby/sigdump/metadata.xml | 8 ++++++++
dev-ruby/sigdump/sigdump-0.2.4.ebuild | 20 ++++++++++++++++++++
3 files changed, 29 insertions(+)
diff --git a/dev-ruby/sigdump/Manifest b/dev-ruby/sigdump/Manifest
new file mode 100644
index 00000000000..66de317f107
--- /dev/null
+++ b/dev-ruby/sigdump/Manifest
@@ -0,0 +1 @@
+DIST sigdump-0.2.4.gem 9216 BLAKE2B 66c3d61eca7f1288de6d95e8d0376d27ab39fee6e5168430801d0f2016f6488eb20cc92e83967d69f690e5ff064952d2696ed08ecd0ab0c4e98c61fdfdbf38cf SHA512 c079f538d3e4e1af61325f18b0580a8d92869800736fc770bc7b193358df480105f1ff223158d52e62ea272e1c375be82ab6415b43c28cc1d74c57cc7640d9cd
diff --git a/dev-ruby/sigdump/metadata.xml b/dev-ruby/sigdump/metadata.xml
new file mode 100644
index 00000000000..28ab0c15f20
--- /dev/null
+++ b/dev-ruby/sigdump/metadata.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<maintainer type="project">
+ <email>ruby@gentoo.org</email>
+ <name>Gentoo Ruby Project</name>
+</maintainer>
+</pkgmetadata>
diff --git a/dev-ruby/sigdump/sigdump-0.2.4.ebuild b/dev-ruby/sigdump/sigdump-0.2.4.ebuild
new file mode 100644
index 00000000000..98006ee4071
--- /dev/null
+++ b/dev-ruby/sigdump/sigdump-0.2.4.ebuild
@@ -0,0 +1,20 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+USE_RUBY="ruby22 ruby23 ruby24 ruby25"
+
+RUBY_FAKEGEM_RECIPE_DOC="rdoc"
+RUBY_FAKEGEM_EXTRADOC="ChangeLog README.md"
+
+RUBY_FAKEGEM_RECIPE_TEST="none"
+
+inherit ruby-fakegem
+
+DESCRIPTION="Setup signal handler which dumps backtrace of threads and allocated objects"
+HOMEPAGE="https://github.com/frsyuki/sigdump"
+LICENSE="MIT"
+
+KEYWORDS="~amd64"
+SLOT="0"
+IUSE=""
next reply other threads:[~2018-04-04 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 19:41 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-28 13:44 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sigdump/ Hans de Graaff
2020-01-05 8:54 Hans de Graaff
2021-11-26 10:06 Hans de Graaff
2022-02-05 6:57 Hans de Graaff
2022-04-22 6:55 Hans de Graaff
2023-07-04 6:01 Hans de Graaff
2023-07-04 6:01 Hans de Graaff
2023-08-26 15:39 Hans de Graaff
2023-12-27 9: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=1522870879.b58d806f665d02ccfd774315584e902492f29875.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