Hello,
I am looking to package two applications that use Node.JS. This email will focus on
one of the two.
Z-Wave JS UI
https://zwave-js.github.io/zwave-js-ui/https://github.com/zwave-js/zwave-js-ui
The application is, I believe, the only open source Z-Wave controller at this time.
I had previously maintained the OpenZWave C++ library, but development on it has
ceased. Z-Wave is a wireless protocol to control lights, switches, relays, or gather
information for uses in home automation. I need to package Z-Wave JS UI to replace
OpenZWave in use with the Domoticz application that I also package.
I first read the Node.JS Packaging Guidelines, but initially struggled to know how
to generate the bundled tarballs. Luckily I stumbled upon the tool to do that via
nodejs-packaging-bundler. After generating an initial RPM spec file I generated an
RPM but it fails to install. Would anyone be able to help?
https://michael.cronenworth.com/RPMS/zwave-js-ui.spechttps://michael.cronenworth.com/RPMS/zwave-js-ui-9.27.2-0.1.fc41.src.rpm
dnf install ...
Problem: conflicting requests
- nothing provides libc++_shared.so needed by zwave-js-ui-9.27.2-0.1.noarch from
@commandline
- nothing provides libc++_shared.so()(64bit) needed by
zwave-js-ui-9.27.2-0.1.noarch from @commandline
- nothing provides libc.musl-x86_64.so.1()(64bit) needed by
zwave-js-ui-9.27.2-0.1.noarch from @commandline
- nothing provides libc.so needed by zwave-js-ui-9.27.2-0.1.noarch from @commandline
- nothing provides libc.so()(64bit) needed by zwave-js-ui-9.27.2-0.1.noarch from
@commandline
[...] snipped out 10 more lines similar to the above...
The second application is the Jellyfin web client. I currently package it via a
bundled tarball generated with my own bash script using a local npm registry and
using npm install. It builds offline, but I notice your packaging guidelines don't
want to do it that way. I'll mold any knowledge gained with zwave-js-ui into
jellyfin-web.
Thanks,
Michael
