pvr.dvblink v3.3.6 (Krypton) Fixed: PVR_TIMER.iClientIndex handling bug #58

[ksooo]

superseeds #59 , fixes #58

thx @dvblogic

[MartijnKaijser]

@dvblogic any chance that you can start tagging your releases on github? That way we can switch from building from this repository to straight do builds using your tagged versions. Once you release a new version you can simply send a PR to update the tag. Thoughts on this?

[dvblogic]

@MartijnKaijser Should be possible. Is there any FAQ or how-to reading on what it is and how to do that?

[MartijnKaijser]

@dvblogic currently not really.
What you basically have to do is tag each release on github which can do with some github client or just online https://github.com/dvblogic/pvr.dvblink/releases

Then we can change to file that point to location to your github repo with the specific tag
https://github.com/xbmc/repo-binary-addons/blob/master/pvr.dvblink/pvr.dvblink.txt
https://github.com/xbmc/repo-binary-addons/blob/Jarvis/pvr.dvblink/pvr.dvblink.txt
You can do this for both Kodi v16 (Jarvis) and v17 (master). Once we branch of v17 into Krypton, master will become the location for v18 developments.

So to start of you should create github release tags to which we can then point to. Once you release a new version you simply only have to change that tag in the txt file