FS#73637 - [electron] standardize electron-based application packaging
Attached to Project:
Community Packages
Opened by BrLi (brli) - Saturday, 05 February 2022, 13:12 GMT
Last edited by Caleb Maclennan (alerque) - Wednesday, 17 May 2023, 13:11 GMT
Opened by BrLi (brli) - Saturday, 05 February 2022, 13:12 GMT
Last edited by Caleb Maclennan (alerque) - Wednesday, 17 May 2023, 13:11 GMT
|
Details
Description:
There are currently plenty of electron-based applications in the official repo. With different package style. Some includes the raw node_modules directory, some are using app.asar There is the execute script, mime-type xml and .desktop, but not all of them are always separated into single file and put to source array. And, most of the time, there are wastes for other OS, or readme, license, dot files etc. in the downloaded node modules, you may also want to avoid them. node-prune is a neat golang-based tool for that. Maybe the team needs to come up with a standardized electron packaging style so that packagers have rules to follow. Additional info: * package version(s) electron9, 11, 12, 13, 14, 15, 16(current latest) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by Caleb Maclennan (alerque)
Wednesday, 17 May 2023, 13:11 GMT
Reason for closing: Not a bug
Additional comments about closing: This isn't an issue with the Electron package, it is a general one with things that depend on Electron. The right way to address this is to work on the Wiki page for Electron packaging guidelines, then point out specific bits from the guidelines that could be used to improve other packages.
Wednesday, 17 May 2023, 13:11 GMT
Reason for closing: Not a bug
Additional comments about closing: This isn't an issue with the Electron package, it is a general one with things that depend on Electron. The right way to address this is to work on the Wiki page for Electron packaging guidelines, then point out specific bits from the guidelines that could be used to improve other packages.
Comment by
Caleb Maclennan (alerque) -
Thursday, 11 May 2023, 14:11 GMT
Having packaged *many* electron apps over the years, I'm not
convinced there even can be a standard set of practices. Almost
every upstream I've ever seen does something differently that
needs to be fiddled with to unbundle things and get them running
with the system electron packages. If somebody wanted to work on
improvements for the Arch Wiki page for Electron guidelines with
preferences for ways to try first and how to handle common
patterns that would be awesome (and I'd even help along the way)
but I really don't know that this should or can be tracked as a
packaging bug because it is so inactionable.