I’m planning to make a common module on which my other add-ons will depend – just so I can get away from manually maintaining this same code in a bunch of addons.
(This common module just has basic typical things like handy constants, some logging stuff, code to get settings in the right way etc).
I can see a few other examples of this (jurialmonkey etc) – but just wanted to check before I go to the effort…in short, it’s just a PITA maintaining code that is the same for 8+ separate addons (4 in the main Kodi repo currently with another two there on the way, plus some in my own repo).
i.e. I want to make & submit to the main Kodi repo:
script.module.bossanova808
And then (or at the same time I guess) – I would modify these add-ons to use it:
[In Kodi Addon Repo]
weather.ozweather
script.service.checkpreviousepisode
script.service.playbackresumer
script.xbmc.unpausejumpback
…plus two new ones – coming Soon to Kodi main repo if all goes to plan]
[In my own repo]
script.kodi.yoctodisplay (uses pre-compiled binaries to talk to hardware, so am told can’t go in main repo)
script.ozweather-skinpatcher (patches a variety of skins for better OzWeather support, am told this is also not suitable for the main repo)
Questions:
Is this ok to do? I.e. will it pass the Kodi repo gatekeepers in this form (i.e. this code is already in the repo, just as 4 separately maintained files currently!)
Is there a better way to approach this?