Then the resulting archive will have the contents of that directory, without that directory, so instead of extracting to:
some-dir/
a
b
c
It'll extract to
a
b
c
ie. it's a "tarbomb".
Adding a --force-wrap option could force butler to consider the contents to be "the parent folder if it only contained some-dir". All the code's already there, so it's "just as simple" as adding the CLI argument, and it's a backwards-compatible change.
On the app side (well, also butler) - we might need to change our .itch.toml lookup routines.
Currently it only looks at the top-level, but if there's nothing there we might want to also look in any subfolders, excluding .itch. This is sorta confusing, but that's the only way to let --force-wrap games ship manifests.
Right now, if you do
Then the resulting archive will have the contents of that directory, without that directory, so instead of extracting to:
It'll extract to
ie. it's a "tarbomb".
Adding a
--force-wrapoption could force butler to consider the contents to be "the parent folder if it only contained some-dir". All the code's already there, so it's "just as simple" as adding the CLI argument, and it's a backwards-compatible change.On the app side (well, also butler) - we might need to change our
.itch.tomllookup routines.Currently it only looks at the top-level, but if there's nothing there we might want to also look in any subfolders, excluding
.itch. This is sorta confusing, but that's the only way to let--force-wrapgames ship manifests.