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/async/
Date: Fri, 30 Jun 2023 05:34:08 +0000 (UTC)	[thread overview]
Message-ID: <1688103232.b536133aa970d6f3534a4276b0174b1c1ba27ee3.graaff@gentoo> (raw)

commit:     b536133aa970d6f3534a4276b0174b1c1ba27ee3
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 30 05:33:52 2023 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Jun 30 05:33:52 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b536133a

dev-ruby/async: add 2.6.2

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

 dev-ruby/async/Manifest           |  1 +
 dev-ruby/async/async-2.6.2.ebuild | 46 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 47 insertions(+)

diff --git a/dev-ruby/async/Manifest b/dev-ruby/async/Manifest
index ed0be9dcf072..dcc690b55430 100644
--- a/dev-ruby/async/Manifest
+++ b/dev-ruby/async/Manifest
@@ -3,3 +3,4 @@ DIST async-1.31.0.tar.gz 92889 BLAKE2B b573e3106243fd0934387254b302f541a9ebbcd34
 DIST async-2.2.1.tar.gz 75671 BLAKE2B a652bbb99d49c569fd864015059391a013f35c888be1e3b32ae06900bb861274390543c64ac9687689cb012c9b4c82df7764e4aaa50d2e76b595fdc7736ec8f5 SHA512 329862fa30f56371092666bef199b949e6325d99696a7ef2029cf9524a5cea31fc361cfaf438e15731c8e09c06ca47261fd3fcdce306a464332def9897c8dec5
 DIST async-2.5.0.tar.gz 84307 BLAKE2B 0aa9042e6e63087c08def6a5bd66f51565addaf8caf1db3ce5cc94afd397e164dfd0e7af40d4f55d05b0bb08cec3c98dc89b5e4345ff053f06617a8ba6a9b0c8 SHA512 caa16d07b2863f236bdd31fc87aa29216a5e32c8182a6e6bf9fd5203cd223350bb1746be02a617f8930c31f2941ce4204f01c5f2fd902c215a1898192afd01c3
 DIST async-2.5.1.tar.gz 84455 BLAKE2B 251b1a8f5bd3d9f1cc4c6038d18dbd5dbe83278d27b35656d12942d7f4501828a2978f64f4fe4e77758476e161e06141b558430af2c42536a7e65bb0795fa2c2 SHA512 b12effeca7372e74ea9ca0ace08d7ea3d7398bbc0c3fdf57f9f57a5888ef975682c86bf010ae1d8b5070408a0f36887972edf12c54382dff5b493d56df5707ac
+DIST async-2.6.2.tar.gz 86923 BLAKE2B ef1a840bd52c3713268582260a00855061fc3ee2d05fb67a2de44f9012dc419745eeac0522fb06e9689860ed23bf5dbb8280f796e645d992d1a98da7cfb4279c SHA512 627f490360d96e9ef8cfb5dc5ea929a1574cdfa6db91fcbfe5b14f6e475e03c750b2806b8d13025425b969ed44944debdcf6d573bc95eafe80a6056a0550707b

diff --git a/dev-ruby/async/async-2.6.2.ebuild b/dev-ruby/async/async-2.6.2.ebuild
new file mode 100644
index 000000000000..625969130dce
--- /dev/null
+++ b/dev-ruby/async/async-2.6.2.ebuild
@@ -0,0 +1,46 @@
+# Copyright 2022-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+# It really is >=ruby31 only, see:
+# https://github.com/socketry/async/issues/141
+# https://github.com/socketry/async/issues/136
+USE_RUBY="ruby31 ruby32"
+
+RUBY_FAKEGEM_RECIPE_TEST="sus"
+RUBY_FAKEGEM_EXTRADOC="readme.md"
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+
+inherit ruby-fakegem
+
+DESCRIPTION="A concurrency framework for Ruby"
+HOMEPAGE="https://github.com/socketry/async"
+SRC_URI="https://github.com/socketry/async/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~sparc ~x86"
+
+ruby_add_rdepend "
+	>=dev-ruby/console-1.10:1
+	dev-ruby/fiber-annotation
+	dev-ruby/io-event:1.1
+	>=dev-ruby/timers-4.1:4
+"
+
+ruby_add_bdepend "test? (
+	dev-ruby/benchmark-ips
+	dev-ruby/sus-fixtures-async
+)"
+
+all_ruby_prepare() {
+	sed -i -E 's/require_relative "(.+)"/require File.expand_path("\1")/g' "${RUBY_FAKEGEM_GEMSPEC}" || die
+
+	# network tests
+	rm test/net/http.rb \
+		test/async/scheduler/address.rb \
+		test/async/scheduler/io.rb || die
+
+	sed -i -e '/covered/Id' config/sus.rb || die
+}


             reply	other threads:[~2023-06-30  5:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  5:34 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-13  4:13 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/async/ Sam James
2024-06-28 12:59 Sam James
2024-02-25  8:52 Hans de Graaff
     [not found] <1708163586.0a5835af33e0d6962a4fad3beb9f503cdbcffa05.graaff@gentoo>
2024-02-17  9:53 ` Hans de Graaff
2024-02-17  9:53 Hans de Graaff
2024-01-03  7:14 Hans de Graaff
2023-10-31  6:42 Hans de Graaff
2023-10-24  9:30 Arthur Zamarin
2023-10-24  9:30 Arthur Zamarin
2023-08-27  6:11 Hans de Graaff
2023-08-09  4:38 Hans de Graaff
2023-07-05  0:04 Sam James
2023-07-04 20:19 Sam James
2023-07-04 20:19 Sam James
2023-07-04 20:19 Sam James
2023-06-30  6:09 Hans de Graaff
2023-05-20  9:21 Sam James
2023-04-09  2:34 Sam James
2023-04-09  2:34 Sam James
2023-04-07  8:39 Sam James
2023-04-07  8:39 Sam James
2023-04-07  8:36 Sam James
2023-04-03  3:17 Sam James
2023-04-03  3:17 Sam James
2023-04-03  0:47 Sam James
2023-04-03  0:47 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
2022-12-05 20:03 Arthur Zamarin
2022-12-01  4:03 Sam James
2022-12-01  4:03 Sam James
2022-12-01  2:04 Sam James
2022-10-23 10:13 Hans de Graaff
2022-10-23 10:01 Hans de Graaff
2022-10-22 21:33 Matt Turner
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=1688103232.b536133aa970d6f3534a4276b0174b1c1ba27ee3.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