New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Addons] Remove noicon/nofanart and old fallback paths to the root of… #17479
Conversation
… the addon directory
Must look which binary addons need update, found icon.png used on 133 and the But from my side no problem to remove and give addon itself the right to give them. As it also standard since v17 😄 |
@AlwinEsch I can make PRs to binary addons that use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
look ok to me
@enen92 just passing on something I found, noicon and nofanart have no analog tags in the new system, they are indicated by simply having an assets tag with no icon or fanart respectively |
I currently add some of the: <assets>
<icon>icon.png</icon>
</assets> to addons where not have. |
Apart from xbmc/vfs.sftp#51 and game.libretro.mame, all binary addons are now correct, although I may have missed one, but shouldn't be much then. I'll take care of it in my rounds. In terms of binaries, the request would be OK for me. |
Reminder to not let the request perish 😄 |
@AlwinEsch I saw you took care of the binary addons. Is still anything left that I need to do? Or can we just invoke build and merge? |
They should all be changed, I look further in future about, but thing there is nothing anymore without |
jenkins build and merge |
Description
This PR removes the fallback behaviour for icon.png and fanart.jpg (as well as the
noicon
andnofanart
elements in addon.xml to avoid the checks).Motivation and Context
Same functionality can be achieved via the
assets
element since krypton. Majority of the addons are python and we have enforced the requirement for the assets element in all repository submissions since the krypton branch.How Has This Been Tested?
Compile and runtime tested
Types of change
Checklist: