Skip to content
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

Merged
merged 1 commit into from Apr 8, 2020

Conversation

enen92
Copy link
Member

@enen92 enen92 commented Mar 11, 2020

Description

This PR removes the fallback behaviour for icon.png and fanart.jpg (as well as the noicon and nofanart 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

  • Bug fix (non-breaking change which fixes an issue)
  • Clean up (non-breaking change which removes non-working, unmaintained functionality)
  • Improvement (non-breaking change which improves existing functionality)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that will cause existing functionality to change)
  • Cosmetic change (non-breaking change that doesn't touch code)
  • None of the above (please explain below)

Checklist:

  • My code follows the Code Guidelines of this project
  • My change requires a change to the documentation, either Doxygen or wiki
  • I have updated the documentation accordingly
  • I have read the Contributing document
  • I have added tests to cover my change
  • All new and existing tests passed

@enen92 enen92 added this to the Matrix 19.0-alpha 1 milestone Mar 11, 2020
@enen92 enen92 requested review from ronie and AlwinEsch March 11, 2020 14:42
@AlwinEsch
Copy link
Member

AlwinEsch commented Mar 11, 2020

Must look which binary addons need update, found icon.png used on 133 and the <icon>[.../]icon.png</icon> only on 108 addons.

But from my side no problem to remove and give addon itself the right to give them.

As it also standard since v17 😄

@AlwinEsch AlwinEsch added Component: Add-ons Type: Cleanup non-breaking change which removes non-working or unmaintained functionality labels Mar 11, 2020
@enen92
Copy link
Member Author

enen92 commented Mar 11, 2020

@AlwinEsch I can make PRs to binary addons that use icon.png and fanart.jpg and don't define them in assets (same for noicon and nofanart). Can you point me to where I can find the whole list of available binary addons?

@enen92 enen92 added the Don't merge PR that should not be merged (yet) label Mar 11, 2020
Copy link
Member

@ronie ronie left a 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

@garbear
Copy link
Member

garbear commented Mar 12, 2020

@AlwinEsch I can make PRs to binary addons that use icon.png and fanart.jpg and don't define them in assets (same for noicon and nofanart). Can you point me to where I can find the whole list of available binary addons?

@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

@AlwinEsch
Copy link
Member

AlwinEsch commented Mar 23, 2020

I currently add some of the:

    <assets>
      <icon>icon.png</icon>
    </assets>

to addons where not have.

@AlwinEsch
Copy link
Member

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.

@AlwinEsch
Copy link
Member

Reminder to not let the request perish 😄

@enen92
Copy link
Member Author

enen92 commented Apr 8, 2020

@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?

@AlwinEsch
Copy link
Member

They should all be changed, I look further in future about, but thing there is nothing anymore without assets.

@enen92 enen92 removed the Don't merge PR that should not be merged (yet) label Apr 8, 2020
@enen92
Copy link
Member Author

enen92 commented Apr 8, 2020

jenkins build and merge

@jenkins4kodi jenkins4kodi merged commit dd156bf into xbmc:master Apr 8, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Apr 8, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request May 5, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 3, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 4, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 4, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 5, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 6, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 6, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 6, 2020
Maven85 pushed a commit to Maven85/kodi that referenced this pull request Aug 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Add-ons Type: Cleanup non-breaking change which removes non-working or unmaintained functionality v19 Matrix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants