From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New Package: RabbitMQ C-Client
Date: Mon, 28 Oct 2019 23:39:53 +0100 [thread overview]
Message-ID: <20191028223953.hXST5VNdczA-5kaKu2YCC0Hosd5Mmy3O5GIKJ0oTkoY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15878@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
There is an updated pull request by schmidh against master on the void-packages repository
https://github.com/schmidh/void-packages rabbitmq-c
https://github.com/void-linux/void-packages/pull/15878
New Package: RabbitMQ C-Client
I'm getting this message:
> WARNING: rabbitmq-c-0.9.0_1: librabbitmq.so.4 not found in common/shlibs!
Can I ignore it or do I have to manually add the new library to common/shlibs?
A patch file from https://github.com/void-linux/void-packages/pull/15878.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rabbitmq-c-15878.patch --]
[-- Type: text/x-diff, Size: 1942 bytes --]
From e3c91a91ef6fdcd26e8069e93217163c776fefe4 Mon Sep 17 00:00:00 2001
From: "Hans-J. Schmid" <knock@myopendoor.de>
Date: Mon, 28 Oct 2019 21:25:22 +0100
Subject: [PATCH] New package: rabbitmq-c-0.9.0
---
common/shlibs | 1 +
srcpkgs/rabbitmq-c-devel | 1 +
srcpkgs/rabbitmq-c/template | 28 ++++++++++++++++++++++++++++
3 files changed, 30 insertions(+)
create mode 120000 srcpkgs/rabbitmq-c-devel
create mode 100644 srcpkgs/rabbitmq-c/template
diff --git a/common/shlibs b/common/shlibs
index 935bc6c9bbd..a79ef996138 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3519,3 +3519,4 @@ libluv.so.1 libluv-1.30.1.0_1
libarmadillo.so.9 armadillo-9.700.2_1
libvarnishapi.so.2 libvarnishapi-6.3.0_1
libicns.so.1 libicns-0.8.1_1
+librabbitmq.so.4 rabbitmq-c-0.9.0_1
diff --git a/srcpkgs/rabbitmq-c-devel b/srcpkgs/rabbitmq-c-devel
new file mode 120000
index 00000000000..5039cc59dce
--- /dev/null
+++ b/srcpkgs/rabbitmq-c-devel
@@ -0,0 +1 @@
+rabbitmq-c
\ No newline at end of file
diff --git a/srcpkgs/rabbitmq-c/template b/srcpkgs/rabbitmq-c/template
new file mode 100644
index 00000000000..2319570d516
--- /dev/null
+++ b/srcpkgs/rabbitmq-c/template
@@ -0,0 +1,28 @@
+# Template file for 'rabbitmq-c'
+pkgname=rabbitmq-c
+version=0.9.0
+revision=1
+build_style=cmake
+hostmakedepends="popt xmlto doxygen"
+makedepends="libressl-devel"
+short_desc="RabbitMQ C client"
+maintainer="Hans-J. Schmid <knock@myopendoor.de>"
+license="MIT"
+homepage="https://github.com/alanxz/rabbitmq-c"
+distfiles="https://github.com/alanxz/${pkgname}/archive/v${version}.tar.gz"
+checksum=316c0d156452b488124806911a62e0c2aa8a546d38fc8324719cd29aaa493024
+
+post_install() {
+ vlicense LICENSE-MIT
+}
+
+rabbitmq-c-devel_package() {
+ depends="${sourcepkg}>=${version}_${revision}"
+ short_desc+=" - development files"
+ pkg_install() {
+ vmove usr/include
+ vmove usr/lib/pkgconfig
+ vmove usr/lib/*.a
+ vmove usr/lib/*.so
+ }
+}
next prev parent reply other threads:[~2019-10-28 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 22:29 [PR PATCH] " voidlinux-github
2019-10-28 22:32 ` voidlinux-github
2019-10-28 22:34 ` voidlinux-github
2019-10-28 22:39 ` voidlinux-github [this message]
2019-10-28 22:39 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-28 23:39 ` [PR PATCH] [Merged]: " voidlinux-github
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=20191028223953.hXST5VNdczA-5kaKu2YCC0Hosd5Mmy3O5GIKJ0oTkoY@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).