From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/slock/
Date: Fri, 6 Nov 2015 04:51:56 +0000 (UTC) [thread overview]
Message-ID: <1446785505.3b10e2078c19c6cd9b6b1fb1def83a488397d2b1.jer@gentoo> (raw)
commit: 3b10e2078c19c6cd9b6b1fb1def83a488397d2b1
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 6 04:51:45 2015 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Fri Nov 6 04:51:45 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3b10e207
x11-misc/slock: Add epatch_user (bug #564744 by aj <AT> xocite.com).
Package-Manager: portage-2.2.24
x11-misc/slock/slock-1.2-r1.ebuild | 59 ++++++++++++++++++++++++++++++++++++++
1 file changed, 59 insertions(+)
diff --git a/x11-misc/slock/slock-1.2-r1.ebuild b/x11-misc/slock/slock-1.2-r1.ebuild
new file mode 100644
index 0000000..0ec1fc8
--- /dev/null
+++ b/x11-misc/slock/slock-1.2-r1.ebuild
@@ -0,0 +1,59 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=5
+inherit eutils fcaps savedconfig toolchain-funcs
+
+DESCRIPTION="simple X screen locker"
+HOMEPAGE="http://tools.suckless.org/slock"
+SRC_URI="http://dl.suckless.org/tools/${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~hppa ~x86 ~x86-fbsd"
+
+RDEPEND="
+ x11-libs/libX11
+ x11-libs/libXext
+"
+DEPEND="
+ ${RDEPEND}
+ x11-proto/xproto
+"
+
+src_prepare() {
+ epatch "${FILESDIR}"/${P}-dontdieonme.patch
+
+ epatch_user
+
+ sed -i \
+ -e '/^CFLAGS/{s: -Os::g; s:= :+= :g}' \
+ -e '/^CC/d' \
+ -e '/^LDFLAGS/{s:-s::g; s:= :+= :g}' \
+ config.mk || die
+ sed -i \
+ -e 's|@${CC}|$(CC)|g' \
+ Makefile || die
+ if use elibc_FreeBSD; then
+ sed -i -e 's/-DHAVE_SHADOW_H//' config.mk || die
+ fi
+ restore_config config.h
+ tc-export CC
+}
+
+src_compile() { emake slock; }
+
+src_install() {
+ dobin slock
+ save_config config.h
+}
+
+pkg_postinst() {
+ # cap_dac_read_search used to be enough for shadow access
+ # but now slock wants to write to /proc/self/oom_score_adj
+ # and for that it needs:
+ fcaps cap_dac_override,cap_sys_resource /usr/bin/slock
+
+ savedconfig_pkg_postinst
+}
next reply other threads:[~2015-11-06 4:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 4:51 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-13 20:57 [gentoo-commits] repo/gentoo:master commit in: x11-misc/slock/ Jeroen Roovers
2016-03-03 17:22 Jeroen Roovers
2016-08-13 8:27 Jeroen Roovers
2016-08-28 8:51 Jeroen Roovers
2016-09-10 12:48 Agostino Sarubbo
2016-09-11 6:07 Jeroen Roovers
2016-11-24 22:36 Jeroen Roovers
2017-01-04 16:56 Agostino Sarubbo
2017-01-04 17:09 Agostino Sarubbo
2017-01-09 13:38 Jeroen Roovers
2017-01-14 13:18 Jeroen Roovers
2017-08-31 10:33 Jeroen Roovers
2017-08-31 10:33 Jeroen Roovers
2020-07-10 12:09 Sam James
2020-11-03 21:55 Georgy Yakovlev
2021-07-03 20:51 Georgy Yakovlev
2021-07-15 21:42 Sam James
2021-07-17 23:18 Sam James
2022-01-02 17:49 David Seifert
2022-10-07 19:09 Georgy Yakovlev
2023-07-07 4:40 Sam James
2023-07-07 4:40 Sam James
2023-07-07 10:14 Sam James
2023-07-08 3:39 Sam James
2024-09-18 20:43 Petr Vaněk
2024-09-18 20:43 Petr Vaněk
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=1446785505.3b10e2078c19c6cd9b6b1fb1def83a488397d2b1.jer@gentoo \
--to=jer@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