Req alternative to prevent abuse of <requires> in addon.xml
#19
For me the main thing is that everything should turn back to "default" once you switch skin back to confluence. There shouldnt be any additional service add-on running in that case, because most of the time the user probably doesnt even know about the fact that he installed it at all when trying out other skins.
In general I´m also not a fan of "disallowing" stuff, but some of the add-ons from Martijn´s list are definitely not neccessary (I would say 3 or 4, if the rest is needed for all the bling bling then I would be fine with it. But script.games.rom.collection.browser as a dependency for example does not really make any sense to me.)
Donate: https://kodi.tv/contribute/donate (foundation), 146Gr48FqHM7TPB9q33HHv6uWpgQqdz1yk (BTC personal)
Estuary: Kodis new default skin - ExtendedInfo Script - KodiDevKit
Reply


Messages In This Thread
RE: alternative to prevent abuse of <requires> in addon.xml - by phil65 - 2015-07-05, 01:14
Skin "REQUIRING" Addons. - by TwistedFaith - 2015-11-07, 10:57
Logout Mark Read Team Forum Stats Members Help
alternative to prevent abuse of <requires> in addon.xml0