From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/pam_mount/
Date: Tue, 12 Apr 2022 11:46:23 +0000 (UTC) [thread overview]
Message-ID: <1649763974.97558f858a1ae18b792716b4f68e0bc2b30f69fe.hanno@gentoo> (raw)
commit: 97558f858a1ae18b792716b4f68e0bc2b30f69fe
Author: Hanno Böck <hanno <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 12 11:46:14 2022 +0000
Commit: Hanno Böck <hanno <AT> gentoo <DOT> org>
CommitDate: Tue Apr 12 11:46:14 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97558f85
sys-auth/pam_mount: Depend on libpcre2.
We were still depending on old libpcre, although upstream
already changed the API to libpcre2.
Bug: https://bugs.gentoo.org/837983
Signed-off-by: Hanno Böck <hanno <AT> gentoo.org>
Package-Manager: Portage-3.0.30, Repoman-3.0.3
sys-auth/pam_mount/pam_mount-2.18-r1.ebuild | 49 +++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/sys-auth/pam_mount/pam_mount-2.18-r1.ebuild b/sys-auth/pam_mount/pam_mount-2.18-r1.ebuild
new file mode 100644
index 000000000000..03fcbd7cc704
--- /dev/null
+++ b/sys-auth/pam_mount/pam_mount-2.18-r1.ebuild
@@ -0,0 +1,49 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DESCRIPTION="A PAM module that can mount volumes for a user session"
+HOMEPAGE="http://pam-mount.sourceforge.net"
+SRC_URI="mirror://sourceforge/pam-mount/${P}.tar.xz"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="~amd64 ~ppc ~x86"
+
+IUSE="crypt ssl selinux"
+
+DEPEND="
+ >=sys-libs/pam-0.99
+ >=sys-libs/libhx-3.12.1:=
+ >=sys-apps/util-linux-2.20:=
+ >=dev-libs/libxml2-2.6:=
+ dev-libs/libpcre2
+ crypt? ( >=sys-fs/cryptsetup-1.1.0:= )
+ ssl? ( dev-libs/openssl:0= )
+ selinux? ( sys-libs/libselinux )"
+RDEPEND="${DEPEND}"
+BDEPEND="virtual/pkgconfig"
+
+PATCHES=(
+ "${FILESDIR}"/pam_mount-2.16-remove-obsolete-openssl-api.patch
+)
+
+src_configure() {
+ econf --with-slibdir="/$(get_libdir)" \
+ $(use_with crypt cryptsetup) \
+ $(use_with ssl crypto) \
+ $(use_with selinux)
+}
+
+src_install() {
+ default
+ use selinux || rm -r "${D}"/etc/selinux
+ dodoc doc/*.txt
+
+ # Remove unused nonstandard run-dir, current version uses
+ # FHS-compatible /run, but has leftover mkdir from old version
+ rm -r "${D}/var/lib"
+
+ find "${ED}" -name '*.la' -delete || die
+}
next reply other threads:[~2022-04-12 11:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 11:46 Hanno Böck [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 13:21 [gentoo-commits] repo/gentoo:master commit in: sys-auth/pam_mount/ Arthur Zamarin
2024-03-22 12:37 Arthur Zamarin
2024-03-22 12:37 Arthur Zamarin
2024-02-06 18:44 Hanno Böck
2022-05-17 9:19 Agostino Sarubbo
2022-05-17 6:53 Jakov Smolić
2022-05-17 6:53 Jakov Smolić
2021-04-29 17:09 Mikle Kolyada
2021-01-09 8:48 Hanno Böck
2021-01-08 17:20 Matt Turner
2020-12-05 18:49 Matt Turner
2020-11-17 16:56 Matt Turner
2020-11-17 16:56 Matt Turner
2020-11-14 20:32 Sam James
2020-11-12 7:41 Sergei Trofimovich
2020-11-12 0:35 Thomas Deutschmann
2020-01-01 16:44 Mikle Kolyada
2019-05-17 8:58 Lars Wendler
2019-04-10 22:31 Matt Turner
2017-03-16 7:12 Michael Weber
2016-09-26 11:11 Hanno Boeck
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=1649763974.97558f858a1ae18b792716b4f68e0bc2b30f69fe.hanno@gentoo \
--to=hanno@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