From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [RFE] calm needs to know about ZStandard compressed archives
Date: Thu, 31 Dec 2020 15:25:40 +0000 [thread overview]
Message-ID: <f47a0f77-36b7-892a-09d9-f077d18f04c8@dronecode.org.uk> (raw)
In-Reply-To: <8735zt7j3t.fsf@Rainer.invalid>
On 25/12/2020 19:59, Achim Gratz wrote:
>
> While waiting for the Perl bootstrap I've been experimenting with having
> cygport produce .tar.zst packages. Calm (mksetupini) does not recognize
> these at the moment, but I've been able to monkey-patch it by adding
> '|zst' in the obvious places. Can this be done officially, please? I
> can't help noting that these really shouldn't be literal strings so that
> you only need to change them in a single place if necessary; so perhaps
> common_constants.py would be a good place for that definition.
Yeah, this list should be done in a less ad-hoc way.
This isn't totally straightforward as calm uses the python tar module to
validate the upload archives, but that doesn't (yet) support zstd
compression.
next prev parent reply other threads:[~2020-12-31 15:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 19:59 Achim Gratz
2020-12-31 15:25 ` Jon Turney [this message]
2020-12-31 15:47 ` Achim Gratz
2020-12-31 15:51 ` Marco Atzeri
2020-12-31 15:52 ` Achim Gratz
2020-12-31 16:01 ` Marco Atzeri
2020-12-31 17:08 ` Jon Turney
2020-12-31 18:33 ` Achim Gratz
2020-12-31 19:05 ` Brian Inglis
2020-12-31 19:18 ` Achim Gratz
2020-12-31 19:29 ` Brian Inglis
2020-12-31 20:03 ` Achim Gratz
2021-01-03 15:19 ` Jon Turney
2021-01-03 15:30 ` Marco Atzeri
2021-01-03 15:57 ` Achim Gratz
2021-01-03 16:22 ` Marco Atzeri
2021-01-04 14:30 ` Jon Turney
2021-01-04 18:35 ` Achim Gratz
2021-01-03 21:55 ` Marco Atzeri
2021-01-10 15:03 ` Jon Turney
2021-01-10 18:32 ` Achim Gratz
2021-01-24 9:35 ` Achim Gratz
2021-02-07 14:05 ` Jon Turney
2021-01-31 17:13 ` Achim Gratz
2021-02-07 14:07 ` Jon Turney
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=f47a0f77-36b7-892a-09d9-f077d18f04c8@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).