chore(public/sendme.sh): POSIX compliance and verbosity

[yermulnik]

• Make if-conditional POSIX compliant to allow for /bin/sh that is not Bash
• Wrap cmdline params to prevent globbing and word splitting
• Add verbosity to tar to allow user to see where the binary is unpacked to

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
iroh-computer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2025 10:25pm

[neuralpain]

Should sed -E be used instead of sed -r for POSIX portability, as mentioned in the sed docs?

  -E, -r, --regexp-extended
                 use extended regular expressions in the script
                 (for portability use POSIX -E).

[yermulnik]

Should sed -E be used instead of sed -r for POSIX portability, as mentioned in the sed docs?

  -E, -r, --regexp-extended
                 use extended regular expressions in the script
                 (for portability use POSIX -E).

On FreeBSD, where sed is POSIX.2 compliant, I can see that it supports -r flag:

     -r      Same as -E for compatibility with GNU sed.

So it should be fine I guess.

UPD: let me know and I can update sed to use -E though.

[neuralpain]

On FreeBSD, where sed is POSIX.2 compliant, I can see that it supports -r flag:

Okay, then there shouldn't be any issues. The current changes are good.

[yermulnik]

@neuralpain Can you please dismiss your changes request?
@Arqu Can you please give this PR a review/approval?
Thanks.

[neuralpain]

@Arqu Can we get an approval for this?