Change the naming scheme of the installers at build time

We'd like to have all produced installers follow a similar naming scheme, for example:

mullvad-browser-{platform}-{version}.{extension}

So for example with Mullvad Browser 12.0.6, we would have:

• mullvad-browser-windows-12.0.6.tar.xz
• mullvad-browser-linux64-12.0.6.tar.xz
• mullvad-browser-macos-12.0.6.tar.xz

Agreed. We should definitely do the same for Tor Browser, but we postponed that to the 12.5 series.

changed the description

added All Platforms Build System labels

added 12.5 stable label

removed 12.5 stable label

added 13.0 stable label

added Roadmap::Future label

added Task label

We didn't do it for 12.5, and I forgot about it for 13.0a1.

Maybe can we link it to 13.0a2?

Maybe can we link it to 13.0a2?

+1

assigned to @pierov

removed Roadmap::Future label

added Next label

changed due date to July 28, 2023

marked this issue as related to tor-browser-build#40902 (closed)

marked this issue as related to tor-browser-build#40901 (closed)

marked this issue as related to tor-browser-build#40829 (closed)

unassigned @pierov

removed due date July 28, 2023

Maybe linux64 should be linux-x86_64, as we might support other 64bit architectures in the future (for example aarch64).

I'm not sure if Windows, should be windows or windows-x86_64. For Tor Browser, we still support i686, so we'll have windows-i686 and windows-x86_64. For mullvad-browser there is only one Windows architecture, but it might still be useful to keep it in the name, in case we add more in the future.

Works for me.

@boklm I agree

I think the tor-expert-bundle follows the above naming scheme, but if not whatever we converge to we should be consistent between both sets of build outputs.

I think the tor-expert-bundle follows the above naming scheme, but if not whatever we converge to we should be consistent between both sets of build outputs.

It looks like tor-expert-bundle is using the scheme $project-$version-$platform.tar.gz rather than $project-$platform-$version.tar.gz.

Should we change tor-expert-bundle to have platform before version?

Sounds like a good plan to me.

For Windows we also have two separate installers for portable and system versions (currently named install and systeminstall). What names should we use for that?

I suggest:

• portable
• install

Yes, install and systeminstall aren't great. portable and install work also for me.

For the portable install we could just ship a zip archive.

Not really, we want to be able to sign it... Unless we start signing all the binaries.

this would be preference if time allows it

mentioned in issue tor-browser-build#40829 (closed)

With the latest version of the patch for tor-browser-build#40829 (closed), the filenames will be:

(tor-browser|mullvad-browser|tor-expert-bundle|geckodriver|mar-tools)(-portable|-install|-debug-symbols|)-(linux-x86_64|linux-i686|windows-x86_64|windows-i686|macos|android-armv7|android-x86|android-x86_64|android-aarch64)-$version.(tar.xz|tar.gz|zip|exe|dmg|apk)

removed the relation with tor-browser-build#40901 (closed)

removed the relation with tor-browser-build#40902 (closed)

marked this issue as related to tor-browser-build#40914 (closed)

marked this issue as related to tor-browser-build#40915 (closed)

mentioned in merge request tor-browser-build!778 (merged)

closing a dupe of tor-browser-build#40829 (closed)

closed

removed the relation with tor-browser-build#40914 (closed)

removed the relation with tor-browser-build#40915 (closed)

marked this issue as related to tor-browser-build#40966 (closed)