Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] common/hooks/do-extract/00-distfiles.sh: support .tar.zst
Date: Sun, 05 Mar 2023 08:55:48 +0100	[thread overview]
Message-ID: <20230305075548.xs_Kwzc46AJ-U0S5VxrrQY4_V-Lo2xM68YG1udRbV00@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42573@inbox.vuxu.org>

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

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

https://github.com/classabbyamp/void-packages tar-zst
https://github.com/void-linux/void-packages/pull/42573

common/hooks/do-extract/00-distfiles.sh: support .tar.zst
bsdtar is built with support for it, so this shouldn't cause issues

<!-- Uncomment relevant sections and delete options which are not applicable -->

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



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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tar-zst-42573.patch --]
[-- Type: text/x-diff, Size: 1912 bytes --]

From bb39c493411b954f7e884334478496448da8cd77 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Fri, 3 Mar 2023 14:25:01 -0500
Subject: [PATCH] common/hooks/do-extract/00-distfiles.sh: support .tar.zst and
 .zst

.tar.zst: bsdtar is built with support for it, so this shouldn't cause issues
.zst: zstd isn't in base-chroot, so it will need to be specified explicitly
---
 common/hooks/do-extract/00-distfiles.sh | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/common/hooks/do-extract/00-distfiles.sh b/common/hooks/do-extract/00-distfiles.sh
index 14503de3ed76..34b89531c96b 100644
--- a/common/hooks/do-extract/00-distfiles.sh
+++ b/common/hooks/do-extract/00-distfiles.sh
@@ -56,9 +56,12 @@ hook() {
 		*.tbz)        cursufx="tbz";;
 		*.tar.gz)     cursufx="tgz";;
 		*.tgz)        cursufx="tgz";;
+		*.tar.zst)    cursufx="tzst";;
+		*.tzst)       cursufx="tzst";;
 		*.gz)         cursufx="gz";;
 		*.xz)         cursufx="xz";;
 		*.bz2)        cursufx="bz2";;
+		*.zst)        cursufx="zst";;
 		*.tar)        cursufx="tar";;
 		*.zip)        cursufx="zip";;
 		*.rpm)        cursufx="rpm";;
@@ -74,13 +77,13 @@ hook() {
 		esac
 
 		case ${cursufx} in
-		tar|txz|tbz|tlz|tgz|crate)
+		tar|txz|tbz|tlz|tgz|tzst|crate)
 			$TAR_CMD -x --no-same-permissions --no-same-owner -f $srcdir/$curfile -C "$extractdir"
 			if [ $? -ne 0 ]; then
 				msg_error "$pkgver: extracting $curfile into $XBPS_BUILDDIR.\n"
 			fi
 			;;
-		gz|bz2|xz)
+		gz|bz2|xz|zst)
 			cp -f $srcdir/$curfile "$extractdir"
 			cd "$extractdir"
 			case ${cursufx} in
@@ -90,9 +93,16 @@ hook() {
 			bz2)
 				bunzip2 -f $curfile
 				;;
-			*)
+			xz)
 				unxz -f $curfile
 				;;
+			zst)
+				if command -v unzstd &>/dev/null; then
+					unzstd $curfile
+				else
+					msg_error "$pkgver: cannot find unzstd bin for extraction.\n"
+				fi
+				;;
 			esac
 			;;
 		zip)

  parent reply	other threads:[~2023-03-05  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 19:26 [PR PATCH] " classabbyamp
2023-03-03 19:31 ` classabbyamp
2023-03-05  6:56 ` sgn
2023-03-05  7:55 ` classabbyamp [this message]
2023-03-05  7:55 ` classabbyamp
2023-03-05  7:57 ` [PR PATCH] [Updated] " classabbyamp
2023-03-07  0:39 ` [PR REVIEW] " sgn
2023-03-07  0:43 ` [PR PATCH] [Updated] " classabbyamp
2023-03-07  4:45 ` [PR PATCH] [Merged]: " classabbyamp

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=20230305075548.xs_Kwzc46AJ-U0S5VxrrQY4_V-Lo2xM68YG1udRbV00@z \
    --to=classabbyamp@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).