From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Achim Gratz <Stromeko@nexgo.de>
Subject: Re: [PATCH cygport] lib/src_postinst.cygpart: parallelize __prepstrip
Date: Sun, 2 Apr 2023 18:39:50 +0100 [thread overview]
Message-ID: <427a2a31-26d1-7d0d-f90f-767546aac933@dronecode.org.uk> (raw)
In-Reply-To: <197d05e2-2308-3a18-abbd-f6ced1c123aa@dronecode.org.uk>
On 30/03/2023 21:34, Jon Turney via Cygwin-apps wrote:
> On 30/03/2023 20:49, Achim Gratz via Cygwin-apps wrote:
>> Jon Turney via Cygwin-apps writes:
>>> On 26/03/2023 19:12, Jon Turney via Cygwin-apps wrote:
> Exchange the while loop using an iffy read construct to a for loop using a temporary file.
I think this change from zero-delimited to whitespace means this will
now fail to handle any filenames containing whitespace correctly?
This commentary doesn't clearly identify what is wrong with the usage of
read here.
> avoid filename collisions by using an
> SHA256 hash of the full file name.
I think there is already a perfectly good, filesystem safe,
computationally cheap unique identifier for each filename, which is it's
ordinal number in the list of filenames we are examining.
'wait -f' seems to be new in bash 5.0. I assume this fails horribly on
earlier bash versions. I'm ok with requiring that, but maybe we should
check the bash version?
On the plus side, the testsuite passes! :)
next prev parent reply other threads:[~2023-04-02 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 18:12 Jon Turney
2023-03-27 18:43 ` Jon Turney
2023-03-30 19:49 ` Achim Gratz
2023-03-30 20:34 ` Jon Turney
2023-04-02 17:39 ` Jon Turney [this message]
2023-04-02 19:28 ` Achim Gratz
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=427a2a31-26d1-7d0d-f90f-767546aac933@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=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).