From: PaperMountainStudio <PaperMountainStudio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] bitlbee: build with pam and ldap support
Date: Fri, 23 Oct 2020 21:43:09 +0200 [thread overview]
Message-ID: <20201023194309.5QfL2eVLfp0CsUqej2fcjtSh-9Nm8GcFQglo_WOJZPw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25827@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
There is an updated pull request by PaperMountainStudio against master on the void-packages repository
https://github.com/PaperMountainStudio/void-packages 0001-bitlbee-build-with-pam-and-ldap-support.patch
https://github.com/void-linux/void-packages/pull/25827
bitlbee: build with pam and ldap support
A patch file from https://github.com/void-linux/void-packages/pull/25827.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-0001-bitlbee-build-with-pam-and-ldap-support.patch-25827.patch --]
[-- Type: text/x-diff, Size: 1703 bytes --]
From 5901a5e9644790682d244553907de67534397a18 Mon Sep 17 00:00:00 2001
From: Paper <paper@tilde.institute>
Date: Fri, 23 Oct 2020 19:06:37 +0200
Subject: [PATCH] bitlbee: build with pam and ldap support
---
srcpkgs/bitlbee/template | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/bitlbee/template b/srcpkgs/bitlbee/template
index 42faeef8d19..76302732248 100644
--- a/srcpkgs/bitlbee/template
+++ b/srcpkgs/bitlbee/template
@@ -1,16 +1,19 @@
# Template file for 'bitlbee'
pkgname=bitlbee
version=3.6
-revision=3
+revision=4
build_style=gnu-configure
configure_args="--etcdir=/etc/bitlbee --pidfile=/run/${pkgname}/${pkgname}.pid
--ipcsocket=/run/${pkgname}/${pkgname}.sock
--strip=0 --otr=plugin
- $(vopt_if purple --purple=1 --purple=0)"
+ $(vopt_if purple --purple=1 --purple=0)
+ $(vopt_if pam --pam=1 --pam=0)
+ $(vopt_if ldap --ldap=1 --ldap=0)"
make_install_args="install-etc"
hostmakedepends="pkg-config asciidoc"
makedepends="libgcrypt-devel libotr-devel libglib-devel gnutls-devel
- $(vopt_if purple libpurple-devel)"
+ $(vopt_if purple libpurple-devel) $(vopt_if pam pam-devel)
+ $(vopt_if ldap libldap-devel)"
short_desc="Brings instant messaging (XMPP, MSN, Yahoo!, AIM, ICQ, Twitter) to IRC"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later"
@@ -18,7 +21,8 @@ homepage="https://www.bitlbee.org/"
distfiles="https://get.bitlbee.org/src/${pkgname}-${version}.tar.gz"
checksum=9f15de46f29b46bf1e39fc50bdf4515e71b17f551f3955094c5da792d962107e
-build_options="purple"
+build_options="purple pam ldap"
+build_options_default="pam"
desc_option_purple="Build with libpurple support"
system_accounts="$pkgname"
next prev parent reply other threads:[~2020-10-23 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 17:09 [PR PATCH] " PaperMountainStudio
2020-10-23 17:36 ` ericonr
2020-10-23 19:43 ` PaperMountainStudio [this message]
2020-10-23 19:43 ` PaperMountainStudio
2020-10-24 22:52 ` [PR PATCH] [Merged]: " Piraty
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=20201023194309.5QfL2eVLfp0CsUqej2fcjtSh-9Nm8GcFQglo_WOJZPw@z \
--to=papermountainstudio@users.noreply.github.com \
--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).