Subject: [alpine-aports] [PATCH] testing/prosody-mod-auth-ldap: New aport

From: Marian Buschsieweke <[email-masked]>
Date: Thu, 17 Aug 2017 19:31:49 +0200

A Prosody authentication plugin which uses LDAP as the backend
https://modules.prosody.im/mod_auth_ldap.html
---
 testing/prosody-mod-auth-ldap/APKBUILD | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 testing/prosody-mod-auth-ldap/APKBUILD

diff --git a/testing/prosody-mod-auth-ldap/APKBUILD b/testing/prosody-mod-auth-ldap/APKBUILD
new file mode 100644
index 0000000000..fd0cb3f232
--- /dev/null
+++ b/testing/prosody-mod-auth-ldap/APKBUILD
@@ -0,0 +1,22 @@
+# Contributor: Marian <[email-masked]>
+# Maintainer: Marian <[email-masked]>
+pkgname=prosody-mod-auth-ldap
+_prosody_mod_name=auth_ldap
+pkgver=20170817
+pkgrel=0
+pkgdesc="A Prosody authentication plugin which uses LDAP as the backend"
+url="https://modules.prosody.im/mod_auth_ldap.html"
+arch="noarch"
+
+license="MIT"
+depends="prosody lua5.1-ldap"
+makedepends=""
+subpackages=""
+source="https://hg.prosody.im/prosody-modules/raw-file/tip/mod_${_prosody_mod_name}/mod_${_prosody_mod_name}.lua"
+options="!check"
+
+package() {
+	cd "$srcdir"
+	install -Dm644 "mod_${_prosody_mod_name}.lua" "${pkgdir}/usr/lib/prosody/modules/mod_${_prosody_mod_name}.lua"
+}
+sha512sums="4be27f11fd202e2dd7e8af193eec44d7131ac40bcb32d3d91981f49ac6b2a05b15570d3f7234b5fed0048542b8539627604a0ec9df1055b4c6a3a2f2faef5b66  mod_auth_ldap.lua"
-- 
2.14.1

---
Unsubscribe:  [email-masked]
Help:         [email-masked]
---

---

From: Timo Teras <[email-masked]>
Date: Mon, 28 Aug 2017 11:06:26 +0300

Hi,

On Thu, 17 Aug 2017 19:31:49 +0200
Marian Buschsieweke <[email-masked]> wrote:

> diff --git a/testing/prosody-mod-auth-ldap/APKBUILD
> b/testing/prosody-mod-auth-ldap/APKBUILD new file mode 100644
> +pkgdesc="A Prosody authentication plugin which uses LDAP as the
> backend" +url="https://modules.prosody.im/mod_auth_ldap.html"
> +arch="noarch"
> +
> +license="MIT"

This refers to 'tip' which basically means 'latest version'. Please use
versioned links, as otherwise the checksums don't match and we cannot
produce consistent builds.

Same applies for the other prosody modules commits.

Thinking more, I'm wondering would it make sense to have one source
package 'prososdy-modules' that packages all the modules and is split
to these different modules then...

I'm marking all the prosody modules as 'changes requested'.

Also one of the modules was incorporated to prosody 0.10. Would it make
sense to first upgrade prosody (or is it still unreleased/unstable
version?).

Timo

---