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/io-event/
Date: Wed,  5 Jun 2024 05:49:33 +0000 (UTC)	[thread overview]
Message-ID: <1717566557.b376416cdb2bb6e368731c6378bc467f207ca578.graaff@gentoo> (raw)

commit:     b376416cdb2bb6e368731c6378bc467f207ca578
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Jun  5 05:07:11 2024 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Jun  5 05:49:17 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b376416c

dev-ruby/io-event: add 1.6.0

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/io-event/Manifest              |  1 +
 dev-ruby/io-event/io-event-1.6.0.ebuild | 36 +++++++++++++++++++++++++++++++++
 2 files changed, 37 insertions(+)

diff --git a/dev-ruby/io-event/Manifest b/dev-ruby/io-event/Manifest
index 33df372c9a5a..e3ef74df09f7 100644
--- a/dev-ruby/io-event/Manifest
+++ b/dev-ruby/io-event/Manifest
@@ -3,3 +3,4 @@ DIST io-event-1.2.2.tar.gz 35405 BLAKE2B 9fb96c920524db8111b8d3650f2559df71e262f
 DIST io-event-1.3.3.tar.gz 46284 BLAKE2B f2d6fe2a1eb3c1d0f26097847b9b0d464fa274d215f620ffa46e7718d89f97a7ff8bb00b145d29763caed527410d0e3040dab313445e11b26b2ef3891d05f604 SHA512 71391822d2664f9c9534cc474b2e9b052d98f44d7c985b768c93ff2956379f2c107094ba4ab9e376bb3820e085f15187f210566229a31ae493334cf4af073bad
 DIST io-event-1.4.4.tar.gz 46919 BLAKE2B c66b410c1eb3e1b398b2ff8f1cad103f0d75e680b2b79ba8e0144ebfe0d0ce29de4996c2c758447c665231c07a939e31af5f3fc47725be33733dcfed8afcd12e SHA512 f8c7503d5d924de2847a57e6af0b01cb8c1638f4b3060a3afc58ca7cc3a719d5df2fa7b83252d1d761f4a3dc8da68b759797e1d1cd6168ad16421924ef3ef316
 DIST io-event-1.5.1.tar.gz 47618 BLAKE2B 239beebca88dac137ab826df0da9f4c7a0b910a9401e46a542dd73a151009ca6d3b0d94584421a039e693e1f5e3f40e37fa98611ff8f603dc5d4bd30bc0788e3 SHA512 71f343ffdcabde14f1737574e66c198934cdf5c88db0c9dc58106da588a7156d4b36cd2a3bd0552758468bcd78c8ee3ae1d59eb0432f7e66f57e3d9dfe75fa3d
+DIST io-event-1.6.0.tar.gz 50641 BLAKE2B f9af9426e2626f101e7ec45ac601e72b60bcda02ae8cdfe659f2440a0c1b084e8a67501104854a7e896864b5a94c624a27b7e013f03df26b1372a098af2ca3d8 SHA512 92ae37e390718b166eeb0fb5ef148f093d90ab623def9cfc9201086fe332b4139c038309ffab9dfd300b80d079bfeeebe14099a1674678f87a60c540570c3526

diff --git a/dev-ruby/io-event/io-event-1.6.0.ebuild b/dev-ruby/io-event/io-event-1.6.0.ebuild
new file mode 100644
index 000000000000..54d45037491d
--- /dev/null
+++ b/dev-ruby/io-event/io-event-1.6.0.ebuild
@@ -0,0 +1,36 @@
+# Copyright 2022-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+USE_RUBY="ruby31 ruby32 ruby33"
+
+RUBY_FAKEGEM_EXTENSIONS=(ext/extconf.rb)
+RUBY_FAKEGEM_EXTRADOC="readme.md"
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+RUBY_FAKEGEM_RECIPE_TEST="sus"
+
+inherit ruby-fakegem
+
+DESCRIPTION="An event loop"
+HOMEPAGE="https://github.com/socketry/io-event"
+SRC_URI="https://github.com/socketry/io-event/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86"
+IUSE="+io-uring"
+
+RDEPEND="io-uring? ( sys-libs/liburing:= )"
+DEPEND="${RDEPEND}"
+
+all_ruby_prepare() {
+	sed -i -E 's/require_relative "(.+)"/require File.expand_path("\1")/g' "${RUBY_FAKEGEM_GEMSPEC}" || die
+
+	# Avoid dependency on unpackaged covered package
+	rm -f config/sus.rb || die
+
+	if ! use io-uring ; then
+		sed -i -e "s:have_library('uring'):have_library('idonotexist_uring'):" ext/extconf.rb || die
+	fi
+}


             reply	other threads:[~2024-06-05  5:49 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  5:49 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-16 11:09 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/io-event/ Hans de Graaff
2025-03-16 11:09 Hans de Graaff
2025-02-08  1:08 Jakov Smolić
2025-01-03 10:26 Hans de Graaff
2024-12-16  6:19 Hans de Graaff
2024-12-08 18:55 Arthur Zamarin
2024-12-01 12:37 Sam James
2024-11-24 10:24 Hans de Graaff
2024-11-15 12:53 Hans de Graaff
2024-11-08  7:48 Hans de Graaff
2024-11-07  7:22 Hans de Graaff
2024-10-13  7:02 Hans de Graaff
2024-10-06 12:01 Sam James
2024-10-06 11:21 Sam James
2024-09-13  4:13 Sam James
2024-06-28 12:59 Sam James
2024-06-28  4:31 Hans de Graaff
2024-06-02  6:41 Hans de Graaff
2024-03-10 15:19 Hans de Graaff
2024-02-27  6:40 Hans de Graaff
2023-12-29  6:58 Arthur Zamarin
2023-12-29  0:24 Sam James
2023-12-28  6:56 Hans de Graaff
2023-10-24  9:30 Arthur Zamarin
2023-10-24  4:42 Hans de Graaff
2023-09-16  5:30 Hans de Graaff
2023-08-27  6:11 Hans de Graaff
2023-07-04 20:19 Sam James
2023-05-20  9:21 Sam James
2023-04-09  2:34 Sam James
2023-04-02 23:07 Sam James
2023-04-02 23:07 Sam James
2023-04-02 23:07 Sam James
2023-04-02 23:05 Sam James
2023-04-02 22:49 Sam James
2023-03-19  7:14 Hans de Graaff
2023-03-19  7:14 Hans de Graaff
2023-01-13  8:28 Hans de Graaff
2022-12-11  6:27 Hans de Graaff
2022-12-04  6:54 Hans de Graaff
2022-10-23 10:13 Hans de Graaff
2022-10-23  8:26 Hans de Graaff
2022-10-22 21:33 Matt Turner

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=1717566557.b376416cdb2bb6e368731c6378bc467f207ca578.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