id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,phab_field
6701,Fix the bundling scripts to work on Linux/Windows,Itms,,"Right now the bundling scripts are tailored for use by the CI, which runs them under macOS.

A couple issues make the scripts not work on Linux:
- [[source:ps/trunk/source/tools/dist/build-archives.sh| build-archives.sh]] has a `/bin/sh` shebang, but contains a bashism in defining `LANGS`. So it should be a `/bin/bash` shebang.
- [[source:ps/trunk/source/tools/dist/build-unix-win32.sh| build-unix-win32.sh]] does not work with Linux `tar`: it fails with `tar: '--same-order' cannot be used with '-c'`.

Extra issue:
- The new way of bundling without a svn export makes `svnversion -n .` spit `27473MP` revision strings. Indeed, deleting incomplete translations marks the repo as modified. This is inconsistent with previous releases and current autobuilds which have `27473P` revision strings.

Additionally, I would like to know how NSISBI was installed on the CI since I could only find it for Windows. This should be documented in [[source:ps/trunk/source/tools/dist/build-unix-win32.sh#L40 | build-unix-win32.sh line 40]].

When using NSISBI on Windows, more issues arise:
- ending `ARCHIVE_PATH` with a reverse slash does not work, and not adding the slash makes the installer put mods under `binaries/data/mods/archives`. It would be necessary to change `ARCHIVE_PATH` to not include the final slash on either platform and change [[source:ps/trunk/source/tools/dist/0ad.nsi#L141 | line 141 of 0ad.nsi]] accordingly.
- MakeNSISW does not provide a way to change the working directory so it cannot find `FileAssociation.nsh` on [[source:ps/trunk/source/tools/dist/0ad.nsi#L9 | line 9 of 0ad.nsi]]. It would be better to put an explicit `${CHECKOUTPATH}\source\tools\dist\FileAssociation.nsh` there.

",defect,new,If Time Permits,Alpha 27,Build & Packages,,,wraitii,