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/libusb/
Date: Sat, 18 Mar 2023 07:17:42 +0000 (UTC)	[thread overview]
Message-ID: <1679123187.5ce86915a6b6bf730dbeb4c54fd6d220d8fc43b2.graaff@gentoo> (raw)

commit:     5ce86915a6b6bf730dbeb4c54fd6d220d8fc43b2
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 18 07:06:27 2023 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Mar 18 07:06:27 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5ce86915

dev-ruby/libusb: add extension installed marker manually

This gem has an extension that is a no-op when using system
libusb. Install the "extension installed" marker manually to make
rubygems happy.

Closes: https://bugs.gentoo.org/901973
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/libusb/libusb-0.6.4-r2.ebuild | 47 ++++++++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)

diff --git a/dev-ruby/libusb/libusb-0.6.4-r2.ebuild b/dev-ruby/libusb/libusb-0.6.4-r2.ebuild
new file mode 100644
index 000000000000..335703d18ed0
--- /dev/null
+++ b/dev-ruby/libusb/libusb-0.6.4-r2.ebuild
@@ -0,0 +1,47 @@
+# Copyright 2022-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+USE_RUBY="ruby27 ruby30 ruby31"
+
+RUBY_FAKEGEM_EXTRADOC="History.md README.md"
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+
+inherit ruby-fakegem
+
+DESCRIPTION="binding that gives Ruby programmers access to arbitrary USB devices"
+HOMEPAGE="https://github.com/larskanis/libusb"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE=""
+
+DEPEND+="virtual/libusb:1"
+RDEPEND+="${DEPEND}"
+
+ruby_add_rdepend "dev-ruby/ffi:0"
+ruby_add_bdepend "test? ( dev-ruby/eventmachine )"
+
+all_ruby_prepare() {
+	sed -e '/mini_portile2/d' \
+		-e 's/git ls-files --/find/' \
+		-i ${RUBY_FAKEGEM_GEMSPEC} || die
+
+	# Avoid tests that try to open devices or depend on specific hardware
+	rm -f test/test_libusb_{bos,descriptors}.rb || die
+}
+
+each_ruby_test() {
+	${RUBY} -I.:lib -e "Dir['test/test_*.rb'].each{|f| require f}" || die
+}
+
+each_ruby_install() {
+	each_fakegem_install
+
+	# This gem includes an extension that does not actually do anything
+	# when using the system libusb, but newer rubygems versions still
+	# require the marker to be present.
+	ruby_fakegem_extensions_installed
+}


             reply	other threads:[~2023-03-18  7:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18  7:17 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-18 10:26 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/libusb/ Hans de Graaff
2024-10-25  6:31 Hans de Graaff
2024-10-25  6:31 Hans de Graaff
2024-04-22  5:55 Hans de Graaff
2024-04-19  6:31 Hans de Graaff
2024-03-04 18:33 Rick Farina
2023-08-29 17:19 Hans de Graaff
2023-08-29 17:19 Hans de Graaff
2023-03-12 12:09 Hans de Graaff
2022-07-20  6:01 Hans de Graaff
2022-06-18  8:40 Hans de Graaff
2019-04-19  5:46 Hans de Graaff
2019-04-18 20:40 Rick Farina

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=1679123187.5ce86915a6b6bf730dbeb4c54fd6d220d8fc43b2.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