From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/google-protobuf/
Date: Sun, 05 Jan 2025 20:35:22 +0000 (UTC) [thread overview]
Message-ID: <1736109244.26c5fc964db725047ea86533d03d2640be61a14d.sam@gentoo> (raw)
commit: 26c5fc964db725047ea86533d03d2640be61a14d
Author: Paul Zander <negril.nx+gentoo <AT> gmail <DOT> com>
AuthorDate: Sun Dec 8 15:04:28 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jan 5 20:34:04 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=26c5fc96
dev-ruby/google-protobuf: add 4.29.2
Signed-off-by: Paul Zander <negril.nx+gentoo <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/39991
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/google-protobuf/Manifest | 1 +
.../google-protobuf/google-protobuf-4.29.2.ebuild | 47 ++++++++++++++++++++++
2 files changed, 48 insertions(+)
diff --git a/dev-ruby/google-protobuf/Manifest b/dev-ruby/google-protobuf/Manifest
index dc70fb48e702..6f57b72a452d 100644
--- a/dev-ruby/google-protobuf/Manifest
+++ b/dev-ruby/google-protobuf/Manifest
@@ -7,3 +7,4 @@ DIST protobuf-27.4.tar.gz 9156456 BLAKE2B 004427f4923e523bf77298600bf91a8fe4ca8b
DIST protobuf-27.5.tar.gz 9153935 BLAKE2B 08b1b5927188e68ef2ae8ce8cdc6f21c34ee8453f4dfaeb362a7f5a5f0ee5ddc24772e5583ab10fbf193aa43e7fdd316e8fbbe4d066df704aef5469dae01fc8d SHA512 bb266483b11268c207aa0e8ce76442351a331f30151586714d57ed7c9bae05f09aabf5042b90eac85658f708671ba0b33c64d1c58a91a24c00bbf4f4ffdce1bb
DIST protobuf-28.0.tar.gz 9259114 BLAKE2B 328e09ebffb296d838557ea72a4fc4da8e0ad5f1edfccebcc8ee7c9e0e74d06e5e6dbad741fd89f6a4502c1cb246a973fd60c035ccdbf89700b7baff49e2a65e SHA512 8745f625ac781f3bbefe9494cbf570143d38aecc1521edef7a52ffb403b8be24df2c71f4f2410b5a5b78a0f3e8a38a7d19be2cf916b1b9125349d2da18262cd1
DIST protobuf-28.3.tar.gz 9256608 BLAKE2B 05162124676abe18300481e9f985fd2cfb09b052d06670a993e79ef02f3daf0d5380b521977ebc2362d4094486151ea285fe1c98a1d2f3799b18a1fa422fdc13 SHA512 a91e175fed7eb01c4240842a5af73a7d3cefccbb10885434bceeb7bc89ab6c56a74912cee290bf46e81d4026f3c9c2b10faad5545816064e215c4bae7908263d
+DIST protobuf-29.2.tar.gz 9348408 BLAKE2B 847798474bc6a76b9badfdbf605e118dece5e321e81242d7fa1bf5f5d17ee05a3d365ec112dc6d861cade97efff8be1d5d04006a5144f613bdb3ff5eacc63b99 SHA512 aeb21773edc3dd92a6c1ba6ccd721cc8a20d61230a5309c75ee3ef19baa554c228a6d1095f191ccc18f10183b646f3140dfe6526f5812bcaa64b7d5260572643
diff --git a/dev-ruby/google-protobuf/google-protobuf-4.29.2.ebuild b/dev-ruby/google-protobuf/google-protobuf-4.29.2.ebuild
new file mode 100644
index 000000000000..c6e6d8b2f63a
--- /dev/null
+++ b/dev-ruby/google-protobuf/google-protobuf-4.29.2.ebuild
@@ -0,0 +1,47 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+USE_RUBY="ruby31 ruby32 ruby33"
+
+RUBY_FAKEGEM_EXTRADOC="README.md"
+
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+
+RUBY_FAKEGEM_EXTENSIONS=(ext/google/protobuf_c/extconf.rb)
+RUBY_FAKEGEM_EXTENSION_LIBDIR=lib/google
+
+inherit ruby-fakegem
+
+PROTOBUF_PV="$(ver_cut 2-)"
+
+DESCRIPTION="Protocol Buffers are Google's data interchange format"
+HOMEPAGE="https://protobuf.dev/"
+SRC_URI="
+ https://github.com/protocolbuffers/protobuf/releases/download/v${PROTOBUF_PV}/${PN##google-}-${PROTOBUF_PV}.tar.gz
+"
+RUBY_S="protobuf-${PROTOBUF_PV}/ruby"
+
+LICENSE="BSD"
+SLOT="0/$(ver_cut 1-3)"
+KEYWORDS="~amd64 ~arm64"
+IUSE="test"
+
+DEPEND=">=dev-libs/protobuf-${PROTOBUF_PV}"
+
+ruby_add_bdepend "test? ( dev-ruby/json dev-ruby/test-unit )"
+
+all_ruby_prepare() {
+ sed -e '/extensiontask/ s:^:#:' \
+ -e '/ExtensionTask/,/^ end/ s:^:#:' \
+ -e 's:../src/protoc:protoc:' \
+ -e 's/:compile,//' \
+ -e '/:test/ s/:build,//' \
+ -i Rakefile || die
+}
+
+each_ruby_prepare() {
+ ${RUBY} -S rake genproto || die
+ ${RUBY} -S rake copy_third_party || die
+}
next reply other threads:[~2025-01-05 20:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 20:35 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-05 20:35 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/google-protobuf/ Sam James
2024-09-05 2:12 Sam James
2024-08-31 9:14 Hans de Graaff
2024-08-21 9:19 Joonas Niilola
2024-07-28 6:52 Hans de Graaff
2024-01-31 12:54 Joonas Niilola
2023-12-27 20:00 Hans de Graaff
2023-08-27 18:56 Arthur Zamarin
2023-07-18 10:09 Hans de Graaff
2023-06-30 9:27 Hans de Graaff
2023-06-29 15:16 Hans de Graaff
2023-04-13 3:03 Sam James
2023-04-13 3:03 Sam James
2022-11-08 6:12 Hans de Graaff
2022-04-10 4:56 Hans de Graaff
2021-10-31 5:57 Hans de Graaff
2021-03-13 7:08 Hans de Graaff
2021-03-13 7:08 Hans de Graaff
2021-01-10 7:51 Hans de Graaff
2021-01-10 7:51 Hans de Graaff
2020-09-15 6:00 Hans de Graaff
2020-09-15 6:00 Hans de Graaff
2020-05-16 5:46 Hans de Graaff
2020-05-16 4:41 Hans de Graaff
2020-02-15 7:45 Hans de Graaff
2020-02-04 6:29 Hans de Graaff
2020-02-04 6:29 Hans de Graaff
2019-12-14 6:45 Hans de Graaff
2019-12-04 6:05 Hans de Graaff
2019-11-26 19:38 Hans de Graaff
2019-11-16 9:13 Hans de Graaff
2019-10-31 6:49 Hans de Graaff
2019-10-03 6:07 Hans de Graaff
2019-10-03 6:07 Hans de Graaff
2019-09-25 6:11 Hans de Graaff
2019-08-07 5:11 Hans de Graaff
2019-07-14 6:32 Hans de Graaff
2019-06-02 6:01 Hans de Graaff
2018-10-21 8:58 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=1736109244.26c5fc964db725047ea86533d03d2640be61a14d.sam@gentoo \
--to=sam@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