From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] common/hooks/do-extract/00-distfiles.sh: support .tar.zst
Date: Fri, 03 Mar 2023 20:26:10 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42573@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
There is a new 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: 1227 bytes --]
From 7a634086f431e0f20a752a0b7c546e7f5881afd4 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
bsdtar is built with support for it, so this shouldn't cause issues
---
| 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--git a/common/hooks/do-extract/00-distfiles.sh b/common/hooks/do-extract/00-distfiles.sh
index 14503de3ed76..cec16d1dead0 100644
--- a/common/hooks/do-extract/00-distfiles.sh
+++ b/common/hooks/do-extract/00-distfiles.sh
@@ -56,6 +56,8 @@ 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";;
@@ -74,7 +76,7 @@ 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"
next reply other threads:[~2023-03-03 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 19:26 classabbyamp [this message]
2023-03-03 19:31 ` classabbyamp
2023-03-05 6:56 ` sgn
2023-03-05 7:55 ` [PR PATCH] [Updated] " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42573@inbox.vuxu.org \
--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).