Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libcap: update to 2.66.
Date: Sun, 05 Feb 2023 19:26:04 +0100	[thread overview]
Message-ID: <20230205182604.Ky0QojjZ9QoksFzoOnlmdQ28qHOI5KJibGb00kZFtxI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41974@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

There is an updated pull request by mhmdanas against master on the void-packages repository

https://github.com/mhmdanas/void-packages libcap-2.66
https://github.com/void-linux/void-packages/pull/41974

libcap: update to 2.66.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/41974.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libcap-2.66-41974.patch --]
[-- Type: text/x-diff, Size: 1574 bytes --]

From 0f80be04f25cc2481c493ef56c3bfc9779e5a72c Mon Sep 17 00:00:00 2001
From: mhmdanas <triallax@tutanota.com>
Date: Mon, 30 Jan 2023 16:45:43 +0000
Subject: [PATCH] libcap: update to 2.67.

---
 srcpkgs/libcap/template | 17 ++++++-----------
 1 file changed, 6 insertions(+), 11 deletions(-)

diff --git a/srcpkgs/libcap/template b/srcpkgs/libcap/template
index 13c13bcd2822..b1586d3dd7ac 100644
--- a/srcpkgs/libcap/template
+++ b/srcpkgs/libcap/template
@@ -1,6 +1,6 @@
 # Template file for 'libcap'
 pkgname=libcap
-version=2.54
+version=2.67
 revision=1
 bootstrap=yes
 build_style=gnu-makefile
@@ -10,20 +10,15 @@ make_use_env=yes
 short_desc="POSIX.1e capabilities suite"
 maintainer="skmpz <dem.procopiou@gmail.com>"
 license="GPL-2.0-only"
-homepage="http://sites.google.com/site/fullycapable/"
+homepage="https://sites.google.com/site/fullycapable/"
 changelog="https://sites.google.com/site/fullycapable/release-notes-for-libcap"
-distfiles="${KERNEL_SITE}/libs/security/linux-privs/libcap2/${pkgname}-${version}.tar.xz"
-checksum=5091b24247999fd7a5e62bd9ac8bc761cda29f9baa0d1a2ca6a46f13891b4f0f
+distfiles="${KERNEL_SITE}/libs/security/linux-privs/libcap2/libcap-${version}.tar.xz"
+checksum=ce9b22fdc271beb6dae7543da5f74cf24cb82e6848cfd088a5a069dec5ea5198
 
 if [ "$CROSS_BUILD" ]; then
 	make_build_args="CROSS_COMPILE=${XBPS_CROSS_TRIPLET}-"
-fi
-
-if [ "$CHROOT_READY" ]; then
-	hostmakedepends="perl"
-	if [ -z "$CROSS_BUILD" ]; then
-		hostmakedepends+=" gperf"
-	fi
+elif [ "$CHROOT_READY" ]; then
+	hostmakedepends="gperf"
 fi
 
 libcap-devel_package() {

  parent reply	other threads:[~2023-02-05 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 16:48 [PR PATCH] " mhmdanas
2023-02-04 21:37 ` [PR REVIEW] " paper42
2023-02-04 21:37 ` paper42
2023-02-05 18:26 ` mhmdanas [this message]
2023-02-05 18:26 ` [PR REVIEW] libcap: update to 2.67 mhmdanas
2023-02-05 18:27 ` mhmdanas
2023-02-05 20:23 ` [PR PATCH] [Merged]: " paper42

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=20230205182604.Ky0QojjZ9QoksFzoOnlmdQ28qHOI5KJibGb00kZFtxI@z \
    --to=mhmdanas@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).