public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] lib/src_prep.cygpart: Fix incorrect options passed to unzstd in unpack()
Date: Fri, 04 Aug 2023 20:14:55 +0200	[thread overview]
Message-ID: <87a5v6u128.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAF8=Xdd=qXFtnX9MQ2-12nUTAcoThNf5S5qz75EHsA7G_qLYEQ@mail.gmail.com> (Yasutaka ATARASHI via Cygwin-apps's message of "Sat, 5 Aug 2023 02:28:14 +0900")

Yasutaka ATARASHI via Cygwin-apps writes:
> Yeah, I also wonder why the --keep option is not used for .gz and .bz2.
> Now, I recognized the reason.

Thanks.

> `unpack()` is expected to extract the files to the current working
> directory regardless of the specified path of the input. Please see
> the usage in `__src_prep()`.
> Therefore, --keep option can't be used simply.

That's true for bunzip2 and gunzip, but not for zstd (where the output
file can be independently specified).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2023-08-04 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 20:55 yak_ex
2023-07-30 12:27 ` Jon Turney
2023-08-04 17:51   ` ASSI
2023-08-07 16:54     ` Jon Turney
2023-08-07 17:28       ` ASSI
2023-07-30 18:31 ` ASSI
2023-08-04 17:28   ` Yasutaka ATARASHI
2023-08-04 18:14     ` ASSI [this message]
2023-08-04 18:39       ` Yasutaka ATARASHI
2023-08-07 16:54         ` Jon Turney
  -- strict thread matches above, loose matches on Subject: below --
2023-07-29  8:23 Yasutaka ATARASHI

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=87a5v6u128.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).