From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/netatalk/
Date: Wed, 11 May 2016 17:53:07 +0000 (UTC) [thread overview]
Message-ID: <1462989177.7f267088defda72c12be777dfa69242f79575e4f.vapier@gentoo> (raw)
commit: 7f267088defda72c12be777dfa69242f79575e4f
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Wed May 11 17:52:00 2016 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Wed May 11 17:52:57 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f267088
net-fs/netatalk: simplify configure a bit
Newer EAPI handles the silent rules for us.
The REQUIRED_USE settings handles the acl/ldap logic,
so no need to duplicate the checks.
net-fs/netatalk/netatalk-3.1.8.ebuild | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/net-fs/netatalk/netatalk-3.1.8.ebuild b/net-fs/netatalk/netatalk-3.1.8.ebuild
index 41d2c5e..3416b1c 100644
--- a/net-fs/netatalk/netatalk-3.1.8.ebuild
+++ b/net-fs/netatalk/netatalk-3.1.8.ebuild
@@ -75,18 +75,11 @@ src_configure() {
append-flags -fno-strict-aliasing
- if use acl; then
- myeconfargs+=( --with-acls $(use_with ldap) )
- else
- myeconfargs+=( --without-acls --without-ldap )
- fi
-
# Ignore --with-init-style=gentoo, we install the init.d by hand and we avoid having
# to sed the Makefiles to not do rc-update.
# TODO:
# systemd : --with-init-style=systemd
myeconfargs+=(
- --disable-silent-rules
$(use_enable avahi zeroconf)
$(use_enable debug)
$(use_enable debug debugging)
@@ -95,8 +88,10 @@ src_configure() {
$(use_enable kerberos krbV-uam)
$(use_enable quota)
$(use_enable tcpd tcp-wrappers)
+ $(use_with acl acls)
$(use_with cracklib)
$(use_with dbus afpstats)
+ $(use_with ldap)
$(use_with pam)
$(use_with samba smbsharemodes)
$(use_with shadow)
next reply other threads:[~2016-05-11 17:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 17:53 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 9:29 [gentoo-commits] repo/gentoo:master commit in: net-fs/netatalk/ Ulrich Müller
2023-10-20 12:53 Hans de Graaff
2023-10-13 14:14 Arthur Zamarin
2023-10-13 2:44 Sam James
2023-10-12 23:32 Sam James
2023-10-08 5:33 Sam James
2023-10-08 5:33 Sam James
2022-07-11 3:10 Sam James
2022-04-10 10:17 Sam James
2022-03-23 0:14 Sam James
2022-02-02 0:08 Sam James
2022-02-01 5:19 Sam James
2022-02-01 4:43 Sam James
2021-06-30 18:40 Sam James
2021-04-28 16:27 Matt Turner
2021-01-27 3:28 Sam James
2021-01-22 16:32 Mikle Kolyada
2020-08-22 8:04 Michał Górny
2020-06-11 13:49 David Seifert
2019-10-12 21:19 Mikle Kolyada
2019-08-11 11:20 David Seifert
2019-08-01 20:01 Andreas Sturmlechner
2019-08-01 19:58 Mikle Kolyada
2019-06-05 6:48 Agostino Sarubbo
2019-02-15 18:42 Mart Raudsepp
2019-01-02 11:39 Justin Lecher
2019-01-02 11:39 Justin Lecher
2019-01-02 11:39 Justin Lecher
2017-11-26 23:11 David Seifert
2017-04-13 17:48 Michael Weber
2016-12-24 10:26 Agostino Sarubbo
2016-12-23 15:33 Justin Lecher
2016-12-18 16:30 Agostino Sarubbo
2016-12-18 16:25 Agostino Sarubbo
2016-12-05 15:02 Pacho Ramos
2016-10-26 16:53 Markus Meier
2016-10-23 20:53 Justin Lecher
2016-10-23 20:53 Justin Lecher
2016-10-02 12:37 Pacho Ramos
2016-03-18 19:11 Michał Górny
2016-01-07 10:38 Justin Lecher
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=1462989177.7f267088defda72c12be777dfa69242f79575e4f.vapier@gentoo \
--to=vapier@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