I don’t see much info around whether it’s acceptable and if so how to package Electron apps for Fedora. There’s a very brief discussion about it here and I’ve been unable to search the devel list. If it’s permitted/possible/practical then there’s an Electron app I would be interested to maintain.
I personally don’t know much about the packaging guidelines, but most (or all?) Electron apps seem to be distributed as flatpak through Flathub, have you considered that? What is the app you would like to maintain?
[Edit] what makes it challenging to distribute Electron apps as native packages is that they depend on very specific component versions like specific NodeJS versions etc. Keeping them synced/compatible with the natively shipped version can be a lot of work.
For example the current NodeJS RPM is 20.12.2 in Updates, but the version in the main repository is still 20.11.1. The official upstream stable NodeJS is 20.17.0, and the new/mainline version is 22.7.0. When modules in the Electron app depend on code that only exists in one of the four NodeJS versions, there would be a problem. Packaging the entire app in a flatpak together with your own NodeJS version solves that completely.
Hi,
Thanks for the reply!
The package I’m looking at is Bruno. I already package it for an internal rpm repo where I work. The RPM works really well and has done so across the past few versions of Fedora. The thing I’m trying to work through is that their build process currently has an RPM target that uses electron builder and thus making it relatively difficult to integrate with Koji since the build process doesn’t give you direct access to an RPM spec file. I could write one of course, but wanted to check, via this post, whether anyone else is doing this sort of thing and specifically with electron-build and the RPM target.