Release archives don't have the intended file tree structure

[murlakatamenka]

Release archive has files like

BepInEx\core\0Harmony.dll

instead of folders with files

 BepInEx
│   ├──  core
│   │   ├──  0Harmony.dll

Guess that's what may happen when you use Windows file separators \ instead of rest of the world's /

[JoeTomkinson]

Apologies, but I can't see an actual bug in this report. You've referenced an archive characteristic (entry names with \ separators) and a speculation about its cause.

If you've hit a failure mode on Steam Deck, Linux, a scripted install, or something else, could you do me a favour and describe it? Then I can see if I have the time to go through and fix it. As written, this is a code-review comment about packaging style, not a bug report.

Am I assuming this is related to Linux or some Linux derivative? Either way, let me know, cheers.

[murlakatamenka]

I've dug into the issue, your reply helped in a way.

The thing is that release archives does not meet the ZIP standard. Quote from the standard:

4.4.17.1 The name of the file, with optional relative path.
The path stored MUST NOT contain a drive or
device letter, or a leading slash. All slashes
MUST be forward slashes '/' as opposed to
backwards slashes '' for compatibility with Amiga
and UNIX file systems etc. If input came from standard
input, there is no file name field.

And the issue with such non-complacent ZIPs only manifests on *nix systems (I use Linux, you're right), here is some reference:

• https://stackoverflow.com/questions/60276764/zip-file-path-separator
• https://superuser.com/questions/1382839/zip-files-expand-with-backslashes-on-linux-no-subdirectories
• Incorrect Path Separators in ZIP Archives Generated on Windows filebrowser/filebrowser#3874 and many other issues like this on GitHub