On 28/09/15 18:18, Iñaki Baz Castillo wrote: > 2015-09-24 15:14 GMT+02:00 Daniel Pocock <dan...@pocock.pro>: >> Can anybody from the JsSIP team comment on this? How do you feel about >> having node-nan 2.x in the dependency hierarchy? Will you continue >> using node-websocket or would you possibly use node-ws[1] instead? >> Using node-ws instead of node-websocket will reduce the number of >> packages we have to keep track of in Debian. > Initially I used node-ws, and removed it in favor of node-websocket > because node-ws was not good for JsSIP needs. There is no way to move > back to node-ws (in fact, I'm now developer of node-websocket).
Thanks for this feedback With the JsSIP move to Node, a lot of dependencies were added and I had to package all of them, including node-websocket. You can see the package details for node-websocket here: https://packages.qa.debian.org/n/node-websocket.html Debian and Ubuntu only allow one version of each dependency on each system. To use node-websocket >= 1.0.22 in Debian stable (via jessie-backports), we will need to either a) have node-nan >= 2.0.x in jessie-backports, or b) adapt node-websocket to support both old and new versions of node-nan using compiler macros, or c) maybe we could split the package to have a browser-only version that doesn't need any of this compiled code? That would be less painful to support.
