Bug Repository XML Bug in Jarvis-Beta3?
#16
tknorris, all addons can reference any other addon (dependencies can sit in any repo). so for that use, you do not need this at all (repo for D would just have the repo for B listed as a dependency).

this functionality is there to serve the need i explained. that this complicates anything is just bollocks, it was exactly 6 lines of code in that patch and they are utterly contained within those 6 lines of code with no additional processing having to happen anywhere else further down the line (it's just the url's for the files in the database that are impacted). alternative is to complicate the repo generation process for everybody, all in the name of somebody's NIH jerking.
Reply
#17
(2015-12-12, 11:15)ironic_monkey Wrote: tknorris, all addons can reference any other addon (dependencies can sit in any repo). so for that use, you do not need this at all (repo for D would just have the repo for B listed as a dependency).

That's only true if they have that other repo installed. 99% of the time they don't have that other repo installed because the user is only installing the repo to get addon D, they don't even know about common module B.
Reply

Logout Mark Read Team Forum Stats Members Help
Repository XML Bug in Jarvis-Beta3?0