public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/libcap/, sys-libs/libcap/files/
Date: Thu,  9 Feb 2017 16:04:23 +0000 (UTC)	[thread overview]
Message-ID: <1486656258.36aff20510b51dfc55d85f1eac4a40eb9295e333.vapier@gentoo> (raw)

commit:     36aff20510b51dfc55d85f1eac4a40eb9295e333
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Thu Feb  9 16:00:02 2017 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Thu Feb  9 16:04:18 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=36aff205

sys-libs/libcap: document gperf logic a bit more

 sys-libs/libcap/files/libcap-2.25-gperf.patch | 9 ++++++---
 sys-libs/libcap/libcap-2.25.ebuild            | 2 ++
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/sys-libs/libcap/files/libcap-2.25-gperf.patch b/sys-libs/libcap/files/libcap-2.25-gperf.patch
index aa67a19db5..86e930f6a4 100644
--- a/sys-libs/libcap/files/libcap-2.25-gperf.patch
+++ b/sys-libs/libcap/files/libcap-2.25-gperf.patch
@@ -1,6 +1,9 @@
-diff -uNr libcap-2.25.ORIG/libcap/Makefile libcap-2.25/libcap/Makefile
---- libcap-2.25.ORIG/libcap/Makefile	2017-02-01 09:58:34.966642226 +0000
-+++ libcap-2.25/libcap/Makefile	2017-02-01 10:01:49.943651936 +0000
+update gperf call to work with gperf-3.1
+
+https://bugs.gentoo.org/604802
+
+--- a/libcap/Makefile
++++ b/libcap/Makefile
 @@ -44,11 +44,12 @@
  	./_makenames > cap_names.h
  

diff --git a/sys-libs/libcap/libcap-2.25.ebuild b/sys-libs/libcap/libcap-2.25.ebuild
index ad5bb12955..08611ed07c 100644
--- a/sys-libs/libcap/libcap-2.25.ebuild
+++ b/sys-libs/libcap/libcap-2.25.ebuild
@@ -16,6 +16,8 @@ SLOT="0"
 KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-linux ~arm-linux ~x86-linux"
 IUSE="pam static-libs"
 
+# While the build system optionally uses gperf, we don't DEPEND on it because
+# the build automatically falls back when it's unavailable.  #604802
 RDEPEND=">=sys-apps/attr-2.4.47-r1[${MULTILIB_USEDEP}]
 	pam? ( virtual/pam )"
 DEPEND="${RDEPEND}


             reply	other threads:[~2017-02-09 16:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 16:04 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-04 11:21 [gentoo-commits] repo/gentoo:master commit in: sys-libs/libcap/, sys-libs/libcap/files/ David Seifert
2021-12-14  0:44 Sam James
2021-11-20  8:29 Sam James
2021-08-30 21:35 Sam James
2021-08-30  6:12 Sam James
2021-08-03 14:17 David Seifert
2021-08-03 10:27 Lars Wendler
2021-05-25 14:19 Lars Wendler
2021-02-05 10:59 Lars Wendler
2020-12-13 14:06 Lars Wendler
2020-10-08 22:53 Thomas Deutschmann
2020-07-13  9:10 Lars Wendler
2020-07-06 18:17 Lars Wendler
2020-05-05  8:25 Lars Wendler
2020-05-05  8:25 Lars Wendler
2020-01-17 14:58 Lars Wendler
2019-12-29  9:40 Lars Wendler
2019-12-28  9:41 Lars Wendler
2019-12-26 12:27 Lars Wendler
2019-12-12 15:05 Lars Wendler
2018-11-21 10:22 Lars Wendler
2018-07-04  8:43 Lars Wendler
2016-02-10  9:05 Lars Wendler

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=1486656258.36aff20510b51dfc55d85f1eac4a40eb9295e333.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