+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222)
+--- Forum: Kodi related discussions (https://forum.kodi.tv/forumdisplay.php?fid=6)
+--- Thread: [Q&A] treat repository.xbmc.org as override repository (/showthread.php?tid=320752)
[Q&A] treat repository.xbmc.org as override repository - ronie - 2017-08-30
this is a continuation of the discussion that took place on this PR:
https://github.com/xbmc/xbmc/pull/12738
feel free to continue the discussion here
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - Lunatixz - 2017-08-30
Awesome addition!! My only concern is beta repositories, I usually push inbetween test builds per user issue; until the issue is soundly fixed.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - bry - 2017-08-30
.dev I believe would be the extension. not final as far as I know.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - User 182116 - 2017-08-30
I'm guessing that this may reduce the amount of 'your addon doesn't work' complaints incorrectly aimed at the official repository.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - learningit - 2017-08-30
This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - learningit - 2017-08-30
(2017-08-30, 01:55)Bluesmanuk Wrote: I'm guessing that this may reduce the amount of 'your addon doesn't work' complaints incorrectly aimed at the official repository.
Yes. Team Kodi has rules about maintenance, any unmaintained add-ons in the official repo are removed or fixed and maintained by other team members.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - Lunatixz - 2017-08-30
(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.
I don't disagree... the main counter argument I always read... concerns locking an open source software only provokes someone to fork and change the code... but isn't this what you'd inevitably want? Isn't there a greater chance that person would end up debranding the project? reducing the trademark issue...
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - rmrector - 2017-08-30
I don't like this approach as-is. Users shouldn't have to recompile just to fix a feature that has been intentionally crippled. While I agree that that the official repo is the one source of truth for add-on IDs, this (and even further) is definitely cutting users to spite the trademark tainters and pirates. This is the wrong place to fight that battle.
Make it another setting next to "Unknown Sources", nevermind that a nefarious add-on could flip it for the user. Another option that still keeps the user in control is to track the repository that each add-on was installed from, and only auto-upgrade to a new version from the same or official repo. Still show other versions if available so that they can be selected, but have some way to tell if it's from a different repo and/or not the official repo, maybe a warning when such a version is selected.
Using a different ID like ".dev" for testing add-ons is a terrible idea for many add-ons; each add-on has separate settings, some shouldn't have two versions active so users must remember to disable stable versions when testing then disable the testing version and re-enable stable when testing is done and/or a new stable version is released, managing skin usage of add-ons and other dependencies is a pain, and add-ons would need to do even more to protect against multiple active versions. Kodi could be extended further to handle these issues, but it still seems a sub-optimal solution. Dev/testing versions would be better handled with "channels" like stable, beta, and nightly/alpha/unstable. An automated update submission to an official nightly and maybe beta channel will reduce the need for external repos in the first place.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - Koying - 2017-08-30
(2017-08-30, 07:38)rmrector Wrote: I don't like this approach as-is. Users shouldn't have to recompile just to fix a feature that has been intentionally crippled. While I agree that that the official repo is the one source of truth for add-on IDs, this (and even further) is definitely cutting users to spite the trademark tainters and pirates. This is the wrong place to fight that battle.
Nope, it's exactly how it should be.
We have reached a point where users honestly have no clue of what is legit or not in the Kodi world, and where legit addons author are afraid to be put in the same bag as piracy ones.
This is open source, and we have it at heart. If you don't like it, fork, adapt, and rebrand if you plan to distribute.
I have zero doubt the existing forks will do it for you, we just don't want to be associated with it.
PS. Any "setting" is a waste of time, as the "wizards", "builds" and whatnot will instantly override it.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - Lunatixz - 2017-08-30
(2017-08-30, 07:38)rmrector Wrote: I don't like this approach as-is. Users shouldn't have to recompile just to fix a feature that has been intentionally crippled. While I agree that that the official repo is the one source of truth for add-on IDs, this (and even further) is definitely cutting users to spite the trademark tainters and pirates. This is the wrong place to fight that battle.
"In reference to a hypothetical senerio, unrelated to the PR and OP"
There was a time I would have agreed with you... However over the past few years I've watched the Kodi community become disjointed; inpart due to the selfish nature of third-party repositorys not associated with Kodi.
One thing should always be clear, if it can... It should be in the official repository!
As a developer I understand there are projects that won't make it into the official repository... But rarely can't this issue be corrected.
Locking things down unfortunately seems like the only rational solution...
Ponder for a moment how much wasted effort is spent dealing with third-party plug-ins, users and their technical issues caused by unorthodox code.
Sent from my SM-G935T
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - enen92 - 2017-08-30
I don't see this as a "locking Kodi thing" but much more as a security feature. I remember to install a russian repository so i could test a service or auxiliar module and that repo overrode my YouTube addon. For the service I checked out the code so i knew what I was installing. As for YouTube...I didn't.
Developers should also make an effort to have their addons updated in the repo (or remove them completely). As a developer, even in the opensource world, there is a commitment one should have with their users. The hardest thing regarding addon development is not producing the addons but to ensure they continue to work flawlessly overtime.
Enviado do meu A0001 através de Tapatalk
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - TheGame1986 - 2017-08-30
(2017-08-30, 08:29)Lunatixz Wrote:(2017-08-30, 07:38)rmrector Wrote: I don't like this approach as-is. Users shouldn't have to recompile just to fix a feature that has been intentionally crippled. While I agree that that the official repo is the one source of truth for add-on IDs, this (and even further) is definitely cutting users to spite the trademark tainters and pirates. This is the wrong place to fight that battle.
There was a time I would have agreed with you... However over the past few years I've watched the Kodi community become disjointed; inpart due to the selfish nature of third-party repositorys not associated with Kodi.
One thing should always be clear, if it can... It should be in the official repository!
As a developer I understand there are projects that won't make it into the official repository... But rarely can't this issue be corrected.
Locking things down unfortunately seems like the only rational solution...
Ponder for a moment how much wasted effort is spent dealing with third-party plug-ins, users and their technical issues caused by unorthodox code.
Sent from my SM-G935T (typie typie)
I understand the 'it should be in the official repo' policy, but what about a user-case like my own where I have written maybe 2-3 add-ons built specifically for my shop (they run a news style screen while playing a spotify playlist and also showing artist and song information).
I work on these at home and push updates to a repository hosted on my business' website.
I won't be able to use vanilla Kodi to do this in these scenario's, will I?
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - Martijn - 2017-08-30
(2017-08-30, 10:59)RayW1986 Wrote:(2017-08-30, 08:29)Lunatixz Wrote:(2017-08-30, 07:38)rmrector Wrote: I don't like this approach as-is. Users shouldn't have to recompile just to fix a feature that has been intentionally crippled. While I agree that that the official repo is the one source of truth for add-on IDs, this (and even further) is definitely cutting users to spite the trademark tainters and pirates. This is the wrong place to fight that battle.
There was a time I would have agreed with you... However over the past few years I've watched the Kodi community become disjointed; inpart due to the selfish nature of third-party repositorys not associated with Kodi.
One thing should always be clear, if it can... It should be in the official repository!
As a developer I understand there are projects that won't make it into the official repository... But rarely can't this issue be corrected.
Locking things down unfortunately seems like the only rational solution...
Ponder for a moment how much wasted effort is spent dealing with third-party plug-ins, users and their technical issues caused by unorthodox code.
Sent from my SM-G935T (typie typie)
I understand the 'it should be in the official repo' policy, but what about a user-case like my own where I have written maybe 2-3 add-ons built specifically for my shop (they run a news style screen while playing a spotify playlist and also showing artist and song information).
I work on these at home and push updates to a repository hosted on my business' website.
I won't be able to use vanilla Kodi to do this in these scenario's, will I?
You will still be able to as for you nothing changes.
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - enen92 - 2017-08-30
You will as long as there is no addon in the repository with the same id. The addon id can be almost anything so do not confuse it with the addon name.
Enviado do meu A0001 através de Tapatalk
RE: [Q&A] treat repository.xbmc.org as override repository Q&A - TheGame1986 - 2017-08-30
(2017-08-30, 11:00)Martijn Wrote: You will still be able to as for you nothing changes.
Ok I think I must have misread then.
I thought the discussion moved to not allowing any repo outside of the Kodi repo, but I'm looking at the Github link and I see that isn't actually the case.
Thanks.