GyulyVGC
App Packaging 📦
(Still incomplete) TODO list about packaging problems/features to be solved/implemented for the various operating systems.
Windows
- [x] MSI Installer
- [x] Sign the Windows Installer (#894)
- [ ] The installer doesn't remove previously installed instances of the app
- [ ] There is a command-line window opening and closing quickly at the end of the Windows setup wizard since no other WixToolset feature for running commands quietly worked as expected.
- [ ] The sample graphics used for the Windows installer should be modified. Since transparency is supported, I suggest the dialog background be limited to the left side only to follow the standards and fix the visual issues there. The same can apply to the banner image, traditionally only an icon was shown on the right side of it.
macOS
- [x] Disk Image and App bundle
- [x] ~~Possibility to run cargo bundle without building again~~ (solved by manually building the .app file)
- [x] Wrapper script should reference the executable using a relative path (#898)
- [ ] The wrapper script to open the app on macOS should be changed (#197)
- [ ] Add Homebrew cask as per #309
- [ ] Sign Disk Image
Linux
- [x] DEB
- [x] RPM
- [x] AppImage (#900)
- [ ] Other kind of packages (?)
- [ ] Build and publish a Debian Source Package
Feel free to list other problems/features that come to your mind and I'll add them @4r7if3x
Could be worth getting an SSL certificate to sign the Windows package. Otherwise Windows Defender gets upset that it is an unknown publisher.
Could be worth getting an SSL certificate to sign the Windows package. Otherwise Windows Defender gets upset that it is an unknown publisher.
Yep, absolutely. I immediately add it to the set of features. And similarly should also be done for macOS...
@GyulyVGC You'd need a registered company and enlist it with D&B to obtain a Code Signing Certificate. Besides, you can buy them cheaper from resellers such as GoGetSSL.
