2020-10-07, 12:40
A made-up use case:
Let's say I have a regular video add-on that can be opened manually by the user.
Alongside this add-on, I want a Service that does some related stuff, and occasionally displays a notification to the user. The service/process should start- and stop along with Kodi, and not be affected by the video add-on.
I would like both the Service and the Add-on to be a single `.zip` so that the user only needs to install one package.
There are a few ways of doing this (like extracting the Service into `/addons` from the video add-on code), but is there a recommended way of handling dependencies like this?
Let's say I have a regular video add-on that can be opened manually by the user.
Alongside this add-on, I want a Service that does some related stuff, and occasionally displays a notification to the user. The service/process should start- and stop along with Kodi, and not be affected by the video add-on.
I would like both the Service and the Add-on to be a single `.zip` so that the user only needs to install one package.
There are a few ways of doing this (like extracting the Service into `/addons` from the video add-on code), but is there a recommended way of handling dependencies like this?