Closed oech3 closed 4 weeks ago
Based on my experience with Linux distributions, different distros have their own ways of doing things.
I'm not sure how helpful a generic template would be if 1. it's easy to create and 2. every distro has its own quirks anyway.
This provides criterions what does Electron support officially.
And I consider imprementing Categories=Network;WebBrowser; MimeType=application/pdf;application/rdf+xml;application/rss+xml;application/xhtml+xml;application/xhtml_xml;application/xml;image/gif;image/jpeg;image/png;image/webp;text/html;text/xml;x-scheme-handler/http;x-scheme-handler/https; Actions=new-window;new-private-window;
(taken from Chromium
) exactry and writing many translations manually is not easy...
@oech3 The entire point of Electron is that it is a framework for apps to use, it is not intended to be used as a standalone web browser. So writing a .desktop file to use it standalone is sort of missing the point of Electron...
If you want to package an app that uses Electron in your distro repositories, you should use the .desktop file in that application's official packages as an inspiration, so a generic template wouldn't be useful for that either.
Actually, it is what I said to Arch. Sorry for requesting this. But I'm fine to hear upstream's opinion.
But, I say some people uses versioned entries as a GUI latest/outdated Electron checker.
Preflight Checklist
Problem Description
Provide (templete of) desktop entry of Electron for Linux. It is easy to create by myself, or distribution-side. But template from upstream's source simplifies build process.
Proposed Solution
Provide (templete of) desktop entry of Electron for Linux.
Alternatives Considered
None
Additional Information
No response