-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a RPM package for jitsi-meet-electro #754
Comments
I've pushed back on having even more targets for this project. We already have a number of first-party builds, and even third-party ones like the flatpack build. The Debian package is there mostly because we distribute all our software as Debian packages. This is not the case for RPM. At most we could build and offer them in the GH releases page. |
Thanks for the answer. Having a stable URL that can redirect to the latest RPM package from GH releases page would be a good step forward. Moot point is how to deal with (security) updates, but we can work forward with other tools (such as fedy) to complement on the end-users side (with advertising the install method and updating by removing and re-installing newer version). |
That's the easy part then, note the "latest" in the URL: https://github.com/jitsi/jitsi-meet-electron/releases/latest/download/jitsi-meet-amd64.deb A good start here would be a PR with the neceessary changes to start building those RPM artifacts. |
This has been open for years with no interest, closing. |
I would like to use a RPM package for jitsi, so it's easier to deploy using RPM based Linux OS (Fedora, EL clones, etc).
Some end-users can eventually use flatpak or appimage on theses systems, but then this doesn't scale when trying to deploy jitsi-meet on seveal system using RPM tooling. (pulp, satellite, etc).
Creating a RPM was easy as using a dedicated "rpm" target along "deb" and appimage and I was able to create rpm locally out of this project, but then there is probably others tuning in order for the build to succeed on the infra side.
As there is already a PR related to deb that will touch the same files, I'm waiting for it to settle so I can start one for RPM:
#734
The text was updated successfully, but these errors were encountered: