The addon is kodi-17 compatible since January 2016 and kodi-18 compatible since December 2016. It seems the major version number is changed with every Kodi release. Moreover several versions are maintained simultaneously, so maybe slotting would be meaningful. Source: https://github.com/kodi-pvr/pvr.hts/blob/master/pvr.hts/changelog.txt https://github.com/kodi-pvr/pvr.hts/releases/
Created attachment 462294 [details] kodi-pvr-hts-4.0.2.ebuild Tested the attached ebuild for media-plugins/kodi-pvr-hts-4.0.2 with media-tv/kodi-17.0 and it worked with media-tv/tvheadend-4.0.9. Obvuiously, it is not yet slotted. It is derived from the other updated plugins (media-plugins/kodi-pvr-*).
Thank you. The [changelog](https://github.com/kodi-pvr/pvr.hts/blob/master/pvr.hts/changelog.txt) mentioned, that the 4.0.2 version is for kodi-18 and 3.4.13 for kodi-17. Does 4.0.2 work with kodi-16 as well? If guess, slotting would be meaningless then.
The ebuild I posted compiles with Kodi 16.1 and does not crash when I enable the addon. Unfortunately, I am currently not with my Tvheadend, so I can not check if it does really work. The way I understand the entry "Initial Kodi v18 version" is, that it is the first version that /can/ be compiled for v18. I have verified 4.0.2 working with Kodi 17 and at least not crashing with 16.1. I can test it with Kodi 16.1 the next week.
I'm not quite sure what I did yesterday but somehow I managed not to realize that I installed media-plugins/kodi-pvr-hts-16_p20160419 together with Kodi 16.1. kodi-pvr-hts-4.0.2 does not build with Kodi 16.1. Sorry for the misinformation. Maybe slotting is an option here?
Created attachment 462388 [details] build.log
Created attachment 462390 [details] emerge --info '=media-plugins/kodi-pvr-hts-4.0.2::andig'
Created attachment 462392 [details] environment
what is the point of slotting kodi plugins when kodi itself is not slotted?
With slotting I meant not the ability to install parallel versions, but different slots for different kodi versions. This would simplify the work for the user. If the user uses a stable kodi (i.e. 16), then he can accept the keyword for "kodi-pvr-hts:kodi-16", if he uses kodi-17 already (or later this year, the betas of kodi-18) he can keyword "kodi-pvr-hts:kodi-17 and still receive updates. The point for slotting is, that the maintainer of kodi-pvr-hts releases not one linear chain of releases, but point-releases for different major versions.
idk, i never noticed such a usage. maybe have a look at x11-base/xorg-drivers ebuilds, that might be more proper way of doing this thing. if there would be ebuild called kodi-plugins-${PV} with use flag for each plugin then by installing this ebuild with appropriate plugins selected (by use flags) and with a specific version of kodi-plugins specified, it would require kodi of the same version and kodi plugins with compatible versions (that is older versions of plugins would be blocked for newer versions of kodi as they do not compile against newer kodi etc).
A kodi-plugins-... ebuild would be a valid solution, too. Especially since a lot of other kodi ebuild are added to the tree. The slot based approach is kind of similar to the whole KDE based ebuilds (check for example media-sound/kid3), that are often not installable in parallel, but indicate with the 4 or 5 slot the affiliation to KDE 4 or 5.
idk if with kodi plugins it is that strict. i suppose that a kodi plugin might be compatible with version of kodi 16 and 17 (or some versions in the future) at the same time but i might be wrong. and if such a plugin would match two kodi "slots", it would be a problem. this info would come handy.
(In reply to Andreas Grosse from comment #5) > Created attachment 462388 [details] > build.log Hi! I have the same error. Do I need to switch first to kodi 18?
attachment 462294 [details] works really fine with Kodi 17.1 (I only had to mask kodi-pvr-hts-16* due to the change of the numbering scheme)
media-plugins/kodi-pvr-hts-4.0.7 works fine (bumping attachment 462294 [details] is fine)
Created attachment 469682 [details] media-plugins/kodi-pvr-hts-4.0.7.ebuild
Created attachment 555924 [details] kodi pvr hts 4.4.2 incase someone is intrested, version bump to latest, works with kodi Leia
fordfrog, Would you mind making me co-maintainer of this package?
(In reply to Craig Andrews from comment #18) > fordfrog, > > Would you mind making me co-maintainer of this package? i'd be glad! :-) i'm short of time :-|
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=139c39312dfecea061893c95276db2d73a17e15f commit 139c39312dfecea061893c95276db2d73a17e15f Author: Craig Andrews <candrews@gentoo.org> AuthorDate: 2018-12-03 19:05:45 +0000 Commit: Craig Andrews <candrews@gentoo.org> CommitDate: 2018-12-03 19:05:45 +0000 media-plugins/kodi-pvr-hts: 4.4.2 version bump Closes: https://bugs.gentoo.org/605914 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Craig Andrews <candrews@gentoo.org> media-plugins/kodi-pvr-hts/Manifest | 1 + .../kodi-pvr-hts/kodi-pvr-hts-4.4.2.ebuild | 35 ++++++++++++++++++++++ .../kodi-pvr-hts/kodi-pvr-hts-9999.ebuild | 8 ++--- media-plugins/kodi-pvr-hts/metadata.xml | 4 +++ 4 files changed, 44 insertions(+), 4 deletions(-)
