Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP] New package: corosync-3.0.2
Date: Sun, 01 Sep 2019 23:24:20 +0200	[thread overview]
Message-ID: <20190901212420.3zEXYIWpQOCqRYynpjEasTO_wRkz69by-mC6-qyhwEc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14061@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

There is an updated pull request by jirib against master on the void-packages repository

https://github.com/jirib/void-packages corosync
https://github.com/void-linux/void-packages/pull/14061

[WIP] New package: corosync-3.0.2
The Corosync Cluster Engine is a Group Communication System with additional features for implementing high availability within applications.

Needed for future pacemaker package.

A patch file from https://github.com/void-linux/void-packages/pull/14061.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-corosync-14061.patch --]
[-- Type: text/x-diff, Size: 5241 bytes --]

From f108a62e5936ae36c5238f8a1236594b68493f88 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ji=C5=99=C3=AD=20B=C4=9Blka?= <jirib79@gmail.com>
Date: Fri, 30 Aug 2019 02:23:31 +0200
Subject: [PATCH] New package: corosync-3.0.2

---
 common/shlibs                        |  7 ++++
 srcpkgs/corosync/INSTALL.msg         |  6 +++
 srcpkgs/corosync/files/corosync.conf | 24 ++++++++++++
 srcpkgs/corosync/files/corosync/run  |  3 ++
 srcpkgs/corosync/template            | 57 ++++++++++++++++++++++++++++
 srcpkgs/corosynclib                  |  1 +
 srcpkgs/corosynclib-devel            |  1 +
 7 files changed, 99 insertions(+)
 create mode 100644 srcpkgs/corosync/INSTALL.msg
 create mode 100644 srcpkgs/corosync/files/corosync.conf
 create mode 100644 srcpkgs/corosync/files/corosync/run
 create mode 100644 srcpkgs/corosync/template
 create mode 120000 srcpkgs/corosynclib
 create mode 120000 srcpkgs/corosynclib-devel

diff --git a/common/shlibs b/common/shlibs
index 655134c53e5..f3df361eedd 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3502,3 +3502,10 @@ liblog4c.so.3 log4c-1.2.4_1
 libqb.so.0 libqb-1.0.5_1
 libusbguard.so.0 usbguard-0.7.5_1
 libknet.so.1 libknet1-1.11_1
+libsam.so.4 corosynclib-3.0.2_1
+libcfg.so.7 corosynclib-3.0.2_1
+libcpg.so.4 corosynclib-3.0.2_1
+libcmap.so.4 corosynclib-3.0.2_1
+libvotequorum.so.8 corosynclib-3.0.2_1
+libquorum.so.5 corosynclib-3.0.2_1
+libcorosync_common.so.4 corosynclib-3.0.2_1
diff --git a/srcpkgs/corosync/INSTALL.msg b/srcpkgs/corosync/INSTALL.msg
new file mode 100644
index 00000000000..16b45796e7b
--- /dev/null
+++ b/srcpkgs/corosync/INSTALL.msg
@@ -0,0 +1,6 @@
+An example configuration file was placed into /etc/corosync/ for test purpose,
+with this configuration Corosync runs a 'voidlinux' cluster only locally.
+
+For real multi-node setup, Corosync uses UDP transport between ports 5404, 5405
+and 5406 for communication. If you are running a firewall, ensure that
+communication on those ports are allowed between the servers.
diff --git a/srcpkgs/corosync/files/corosync.conf b/srcpkgs/corosync/files/corosync.conf
new file mode 100644
index 00000000000..2eaed8ba7ef
--- /dev/null
+++ b/srcpkgs/corosync/files/corosync.conf
@@ -0,0 +1,24 @@
+# Please read the corosync.conf.5 manual page
+totem {
+        version: 2
+        cluster_name: voidlinux
+
+}
+
+logging {
+        to_stderr: yes
+        to_logfile: yes
+        logfile: /var/log/corosync/corosync.log
+}
+
+quorum {
+        provider: corosync_votequorum
+}
+
+nodelist {
+        node {
+                name: node1
+                nodeid: 1
+                ring0_addr: 127.0.0.1
+        }
+}
diff --git a/srcpkgs/corosync/files/corosync/run b/srcpkgs/corosync/files/corosync/run
new file mode 100644
index 00000000000..5b597145ee4
--- /dev/null
+++ b/srcpkgs/corosync/files/corosync/run
@@ -0,0 +1,3 @@
+#!/bin/sh
+[ -r conf ] && . ./conf
+exec /usr/bin/corosync -f ${OPTS:-}
diff --git a/srcpkgs/corosync/template b/srcpkgs/corosync/template
new file mode 100644
index 00000000000..8df9e202c46
--- /dev/null
+++ b/srcpkgs/corosync/template
@@ -0,0 +1,57 @@
+# Template file for 'corosync'
+pkgname=corosync
+version=3.0.2
+revision=1
+build_style=gnu-configure
+configure_args="--disable-static --enable-monitoring --enable-snmp
+ --enable-xmlconf --with-logdir=/var/log/corosync"
+make_dirs="/etc/corosync/uidgid.d 0755 root root
+ /etc/corosync/service.d 0755 root root
+ /var/log/corosync 0755 root root
+ /var/lib/corosync 0755 root root"
+hostmakedepends="autoconf automake libtool pkg-config"
+makedepends="libqb-devel libstatgrab-devel libtool net-snmp-devel nss-devel"
+short_desc="Cluster engine daemon and utilities"
+maintainer="Jiří Bělka <jirib79@gmail.com>"
+license="BSD-2-Clause"
+homepage="http://corosync.github.io/corosync"
+distfiles="https://github.com/${pkgname}/${pkgname}/releases/download/v${version}/${pkgname}-${version}.tar.gz"
+checksum=f237e3ddac41ec583cac9610a9ba9191592f09d3ed70bc687db7b60e3d2e26f5
+
+# libknet1 is default transport but does not work with musl now
+case "$XBPS_TARGET_MACHINE" in
+        *-musl) :;;
+        *) makedepends+=" libknet1-devel";;
+esac
+
+pre_configure() {
+	autoreconf -vi
+}
+
+post_install() {
+	rm -f ${DESTDIR}/etc/corosync/corosync.conf.example
+	rm -rf ${DESTDIR}/etc/init.d
+	rm -rf ${DESTDIR}/usr/lib/corosync/*.la
+	vinstall ${FILESDIR}/corosync.conf 644 etc/corosync
+	vlicense LICENSE
+	vsv corosync
+}
+
+corosynclib_package() {
+	short_desc="Corosync libraries"
+	pkg_install() {
+		vmove "usr/lib/*.so*"
+		vlicense LICENSE
+	}
+}
+
+corosynclib-devel_package() {
+	depends="corosynclib>=${version}_${revision}"
+	short_desc="Corosync libraries (development files)"
+	pkg_install() {
+		vmove usr/include/corosync
+		vmove "usr/lib/*.so"
+		vmove "usr/lib/pkgconfig"
+		vmove usr/share/man/man3
+	}
+}
diff --git a/srcpkgs/corosynclib b/srcpkgs/corosynclib
new file mode 120000
index 00000000000..f52d533f823
--- /dev/null
+++ b/srcpkgs/corosynclib
@@ -0,0 +1 @@
+corosync
\ No newline at end of file
diff --git a/srcpkgs/corosynclib-devel b/srcpkgs/corosynclib-devel
new file mode 120000
index 00000000000..f52d533f823
--- /dev/null
+++ b/srcpkgs/corosynclib-devel
@@ -0,0 +1 @@
+corosync
\ No newline at end of file

  parent reply	other threads:[~2019-09-01 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14061@inbox.vuxu.org>
2019-09-01 21:13 ` voidlinux-github
2019-09-01 21:13 ` voidlinux-github
2019-09-01 21:24 ` voidlinux-github [this message]
2019-09-01 21:24 ` voidlinux-github
2019-09-01 21:54 ` voidlinux-github
2019-09-01 21:55 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-01 21:55 ` voidlinux-github
2019-09-05 10:28 ` voidlinux-github
2019-09-05 10:28 ` voidlinux-github
2019-09-05 11:22 ` [PR PATCH] [Closed]: " 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=20190901212420.3zEXYIWpQOCqRYynpjEasTO_wRkz69by-mC6-qyhwEc@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).