-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(bundler): output file name consistency, closes #10465 #10577
Conversation
Package Changes Through a9af8ccThere are 7 changes which include tauri-build with prepatch, tauri-codegen with prerelease, tauri-utils with prerelease, tauri-cli with prerelease, @tauri-apps/cli with prerelease, tauri with prerelease, tauri-bundler with prerelease Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
language, | ||
); | ||
let msi_name = | ||
crate::bundle::bundle_name_with_suffix(settings, &language.replace('-', "_"), "msi"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably revert this change, -
(hyphen) is the separator in language tags per the IETF standard https://en.wikipedia.org/wiki/IETF_language_tag#Syntax_of_language_tags
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well that's true, but with this change it's also the separator for the parts in the bundle file name.. I'd prefer using _
instead, but some people prefer -
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there will always people wanting it the other way around but I don't see an issue with App-1.2.0-x64-en-US.exe
, seems better than App-1.2.0-x64-en_US.exe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there will always people wanting it the other way around but I don't see an issue with
App-1.2.0-x64-en-US.exe
, seems better thanApp-1.2.0-x64-en_US.exe
I think this is about consistency rather than standards. The hyphen(-) is a separator between different parts of the filename, while the underscore(_) is a separator between words within a part, such as Snow_White-v1.0.1_beta1-x86_64-en_US.deb. Under the consistent naming convention, it is easy to parse the various standard-compliant parts.
Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>
Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>
Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>
let's at least hold on merging this one, must be communicated (ideally released as the last RC or perhaps even the first 2.0 stable release) |
This is missing explicit Arm + AppImage support - noticed because of #10619 (arm64 currently works, but i apparently didn't test arm 32bit which doesn't work). Expanding this condition for arm->armhf should be enough i think https://github.com/tauri-apps/tauri/blob/dev/tooling/bundler/src/bundle/linux/templates/appimage#L14 |
Co-authored-by: Fabian-Lars <fabianlars@fabianlars.de>
closing this one as it's too late for such a huge change that impacts everyone shipping Tauri apps.. see you in v3 |
I'm still not sure if we want to keep the release tag in the RPM file name, but I'll keep it for now.
Mainly wanted to raise awareness on this issue first.
I like the consistency of this, but I'm also not really a fan of using
-
instead of_
as separator.Note that
-
is also the separator used on the language string currently appended to the MSI file name. I think I'll just change that to use_
instead.