You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we build rpms and debs for Linux. And this is broken in so many way:
it's not normal when rpm and deb packaging on the developer side, this should be done in distributions by maintainers but it's almost impossible to include electron application into the popular linux distributions
updates can be shipped only by creating repositories with all that huge pain with building, signing, forcing user to add repositories configuration to their systems
rpm and deb targets are not first class citizens of electron-builder
we can't create file/url associations (see previous paragraph)
desktop entry for program are broken and can't be fixed because of electron-builder:
spaces in the path - breaks some utilities
path in the quotes - breaks more utilities (hello i3 users)
%U as argument just make program unusable on Mate/KDE
%U as argument force file paths in url style (file://...) - we doesn't support this
All these problems are likely to never be fixed.
Better alternatives: flatpak and snap. This should seize all major distributions. Also, build and host on flathub.org and snapcraft.io marketplaces -> more users. But, electron-builder can't do flatpak (required to use another build procedure). snap is also not easy peasy. So, flatpak and snap look more like a bright future.
Not perfect at all but realistic and practical solution is AppImage. It's like 'portable' one-file univarsal version with some integration with the system.
Pros:
should be more understandable by users (it's just click-and-run file!)
we can enable updates for linux that are consistent with win and mac
user rights are sufficient for installing and upgrading
all problems with desktop entry file are gone (created on first run with user want integration)
mime types created for all xod file types
file associations created and just works
Cons:
needs much testing
require some transition period
(may be) require changes in CI/CD
(may be) require some changes of releases endpoint
require changes in site's download page
For testing purpose I changed root package.json with this build section:
Currently, we build
rpm
s anddeb
s for Linux. And this is broken in so many way:electron
application into the popular linux distributionsrpm
anddeb
targets are not first class citizens ofelectron-builder
electron-builder
:file://...
) - we doesn't support thisAll these problems are likely to never be fixed.
Better alternatives:
flatpak
andsnap
. This should seize all major distributions. Also, build and host on flathub.org and snapcraft.io marketplaces -> more users. But,electron-builder
can't do flatpak (required to use another build procedure).snap
is also not easy peasy. So,flatpak
andsnap
look more like a bright future.Not perfect at all but realistic and practical solution is
AppImage
. It's like 'portable' one-file univarsal version with some integration with the system.Pros:
Cons:
releases
endpointFor testing purpose I changed root
package.json
with this build section:The text was updated successfully, but these errors were encountered: