Re:Show HN: People forget that you can stick any data at the...
by sudobash1 on Wednesday July 05, 2023 @07:05PM
(#36608457)
An even simpler way would be to include a marker to denote the end of the shell script, and the start of the data. For example, if you put this in extract.sh
and then run:
You can then run foobar.tar.gz.sh to self-extract. And you still get the benefit of being able to modify the shell script without needing to count lines or characters without sacrificing any compression.
[ Parent
| on HN ]
Re:Show HN: People forget that you can stick any data at the...
by oxygen_crisis on Thursday July 06, 2023 @03:16AM
(#36612401)
You've already got a marker to denote the end of the shell script baked in there, it's ^exit$
Re:Show HN: People forget that you can stick any data at the...
by withinboredom on Thursday July 06, 2023 @03:54AM
(#36612658)
There may be more than one exit.
Re:Show HN: People forget that you can stick any data at the...
by oxygen_crisis on Thursday July 06, 2023 @04:16AM
(#36612830)
There will be only one that is neither preceded by indentation nor followed by an exit code, so that it could match ^exit$, unless you contrive some hypothetical nonsense purely for the sake of contrarianism.
Any reasonable person will indent a conditional exit within the block testing its condition, and more than one unconditional exit doesn't make sense.
Re:Show HN: People forget that you can stick any data at the...
by withinboredom on Thursday July 06, 2023 @12:03PM
(#36618094)
Ah fair enough. I didn’t think about using the indent, that’s pretty clever.
Re:Show HN: People forget that you can stick any data at the...
by 8n4vidtmkvmk on Thursday July 06, 2023 @12:47PM
(#36618838)
It would still make me uncomfortable that a 2nd exit or lack of indent would break my script. And it's less clear than an explicit marker