Remove `Conflict` directive for better compatibility?

[jotaen4tinypilot]

We declare three packages (libnice10, libsrtp2-1, libwebsockets16) as conflicting, because we are compiling them from source in order to get a version newer than the one from apt.

This restriction caused trouble for us during the update process (2.4.1 → 2.5.0). The problem might re-appear, since all three of these packages are generic utilities that could be installed by other system packages that we might want to install in the future.

So I’m wondering whether the Conflict: directive is really necessary, or whether there would be a way for both versions to safely co-exist on the system. I.e., that Janus internally is linked to libnice10 as compiled by us, whereas other system packages use the one installed via apt.

I don’t know whether that’s possible at all, but maybe it’s an option for us to consider in case this problem occurs again at some point.

[jotaen4tinypilot]

For reference: the predecessor of this Debian package, ansible-role-janus-gateway, also had both at the same time:

• libnice10 had been installed as system package. It came in indirectly as a dependency of gstreamer1.0-plugins-bad at the very beginning of the installation process.
• But it was also built from source during the installation process, and Janus was apparently linked to that as opposed to the system one.

[jotaen4tinypilot]

Obsolete via https://github.com/tiny-pilot/janus-debian/pull/7.