Allow update to only Eden?
#1
I'm trying to restrict an addon update to only Eden users, I must be missing something as so far anything I've added to my addon.xml hasn't stopped Dharma users from installing

At first I was assuming that setting Python to 2.0 would have done it, but no luck there

Is there anything else I can do?

Here's what we have in the requires section:

Code:
<requires>
        <import addon="xbmc.python" version="2.0"/>
        <import addon="script.module.simplejson" version="2.0.10"/>
        <import addon="script.module.elementtree" version="1.2.7"/>
        <import addon="script.module.metahandler" version="0.0.1"/>
        <import addon="script.module.t0mm0.common" version="0.0.1"/>
        <import addon="script.common.plugin.cache" version="0.9.0"/>
    </requires>
Reply
#2
dharma does not have proper python version import handling, this will work for eden+.

also this is precisely why we opted for separate official repos.
Reply
#3
You Could try adding a common used module that is only used in the eden repo (even if you don't actualy use it).
This way they get dependancy not met.
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#4
I was assuming common cache was Eden only?
Reply
#5
Eldorado Wrote:I was assuming common cache was Eden only?

hmm indeed.
Maybe this only works on Eden+ the dependencies not met?
I thought it also worked on Dhama
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#6
Martijn Wrote:hmm indeed.
Maybe this only works on Eden+ the dependencies not met?
I thought it also worked on Dhama

We had one user who was able to install an update after we put in common cache as a required.. and of course got a script error on the import

It's odd since I had other addons that showed as 'Broken' due to missing dependencies

I'm going to try again soon, install 10.1 and see what happens!
Reply
#7
Just bringing this one back as I've been testing this more and it doesn't seem I can stop an addon from updating in Dharma, even if dependencies are not available

Is this just due to Dharma not being able to check properly?

My addon.xml has this:
Code:
<requires>
        <import addon="xbmc.python" version="2.0"/>
        <import addon="script.module.simplejson"/>
        <import addon="script.module.elementtree"/>
        <import addon="script.module.beautifulsoup"/>
        <import addon="script.module.metahandler" version="0.0.1"/>
        <import addon="script.module.t0mm0.common" version="1.1.0"/>
        <import addon="script.common.plugin.cache" version="0.9.0"/>
    </requires>

I removed everything, installed XBMC 10.1 and installed the current release of my addon.. no problems

I then install the repository where we are developing the Eden version with the above addon.xml

The addon updates without checking it's dependencies and of course fails when trying to run due to not being able to find the common cache script

Also noting I set 'script.module.t0mm0.common' to version 1.1.0 which is the Eden version, I checked and it download the Dharm version 1.0.0

Is there anything else I can do?
Reply
#8
Correct. As spiff said "dharma does not have proper python version import handling, this will work for eden+."
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


Image
Reply
#9
jmarshall Wrote:Correct. As spiff said "dharma does not have proper python version import handling, this will work for eden+."

Ah.. I was taking that as meaning it only applied to setting python=2.0

Was hoping missing dependencies would stop it

thanks!
Reply

Logout Mark Read Team Forum Stats Members Help
Allow update to only Eden?0