Closed lazerdude7 closed 4 months ago
It feels then that distros based on RPM packages are quite a mess when it comes to package name standarisation and interoperability to support all.
I guess I'm not going to care about packaging 99 versions of RPM for each distro, just because a name contains one char more, different char casing or one char replaced with another (ex. for gtk3
: gtk-3
, gtk_3
, gtk+3
, GTK3
...). After all it's all Electron Forge and each of their components (includibg third-party ones) to take care of the app packaging.
This means, the issue is clearly an upstream one, I would criticize distros for not taking care of standarizing their package dependencies enough, but you might as well discuss that with Forge if you want. For me this issue is surely to be closed and not taken care of at all. After all, why should I when it's not WebCord that implements the whole packaging logic?
Acknowledgements
[X] I have checked that there is no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
[ ] This bug affects Discord website.
[ ] This issue is confirmed to be reproducible when WebCord is packaged on at least all three latest supported Electron major releases.
[ ] This issue is reproducible in Chrome, Chromium or any Chromium-based browser, e.g Brave or Edge (please write in Additional Context which browser you have used if it is neither Chrome nor unmodified Chromium).
[ ] There are no fixes done to
master
which resolves this issue.[ ] My issue describes one of the unstable and/or not fully implemented features.
[ ] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).
Operating System / Platform
🐧️ Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
N/A
Application version
v4.8.0
Bug description
Attempting to install the latest RPM release of WebCord using DNF package manager on Mageia 9 system results in the following error:
It is likely due to the dependency names being slightly different on this distribution, as if I check for similarly named installed packages, I get the following:
It may be possible to force install the package using RPM directly, but I have not attempted it.
The AppImage version however works fine, and it is understandable if you do not want to add support to this distribution via the RPM package.
Additional context
No response