ermo Probably talking about their configuration and choice of add-ons.

    16 days later

    DataDrake Yes, but some people compile out-of-tree addons so I was curious what those were (so that I know what add-ons are known to work if other people come asking).

    2 months later
    • [deleted]

    • Edited

    ermo Thank you once again, been watching some movies on my "unstable" setup, and have not had any issues with it.

    2 months later

    I landed Kodi 18.7 this past Monday. It will hit the stable branch during the next sync.

    2 months later

    I landed Kodi 18.8 this past Wednesday. It should have hit the stable branch by now.

    2 months later

    This is a heads up that I'm currently investigating whether it would be better to stop offering a Solus-specific Kodi build and instead point people to the flatpak version of Kodi.

    The main reason is that upstream will no longer officially support the convenient "batteries-included" build that I'm currently doing once kodi v19 "Matrix" lands (unless the build is done with PREFIX=/usr/local).

    Kodi v19 "Matrix" is currently in alpha and upstream has indicated that Kodi v18.8 will be the last update to the "Leia" branch. The Kodi version available on flathub is v18.8 as of this writing.

      ermo I have two KODI versions installed and I use Solus-specific Kodi build. The flatpak version is just a back-up. I guess I am not care about "batteries-included" (preinstalled addons, right?)

      My concerns about flatpak version are:

      • will there be a delay for the flatpak releases
      • I have to figure out how to transfer my library/favorites/addon settings (not a big problem)

      Is there a simple way to test alpha v19 on Solus?

      • ermo replied to this.

        Solarmass

        From an official Solus packaging perspective, there's obviously the option to build only the main kodi distribution and the kodi-platform package.

        This would allow users to follow a guide in order to build the binary add-ons from e.g a from-source package.yml via solbuild and have said locally-built package install to /usr/local.

        However, I'm not sold on this option as it will break every time there is a kodi rebuild.

        But to answer your actual question:

        Right now, there's no simple way to test alpha v19 on Solus unless you want to build the package yourself -- either directly from source or via a locally written package.yml, which builds to an installable .eopkg using solbuild configured with a local repository.

          ermo This would allow users to follow a guide in order to build the binary add-ons from e.g a from-source package.yml via solbuild and have said locally-built package install to /usr/local.

          Can you give some examples of these binary add-ons? It is not YouTube add-on.

          However, I'm not sold on this option as it will break every time there is a kodi rebuild.

          Not a great experience, yes

          Right now, there's no simple way to test alpha v19 on Solus unless you want to build the package yourself -- either directly from source or via a locally written package.yml, which builds to an installable .eopkg using solbuild configured with a local repository.

          Thanks. I think the simple way to test it would be in the Windows VM.

          10 days later

          Just successfully built Kodi 18.9 locally. Will try to get it pushed to -unstable along with a samba stack upgrade over the weekend/early next week.

          19 days later
          3 months later
          7 days later

          I just had Kodi 19 update on my mobile phone and it broke all of my add-ons, is there a way I could edit a conf file for sudo eopkg up to exclude kodi from future updates(since it might take awhile until these add-ons start working on this version) It seems natural that I could do sudo eopkg up --exclude kodi but it would be great if I could edit it in a conf file till the inevitable future!

            laky
            No. An its not feasible to hold back manually for an indefinite period of time either. The last two Kodi updates Solus made were rebuilds against updated dependencies.

            • laky replied to this.

              Harvey Meaning the involved dependencies that might get updated would break the old kodi version? Well that is a shame , but thanks for clearing it up.

                laky

                Yeah, it is why partial updates are not supported. They are the number one cause of breakages. An I promise you something will break eventually and in a way more spectacular fashion than some Kodi addons not working.

                EDIT:
                I know flatpak's did not used to update themselves automatically a few years ago. If that is still the case or there is a way to stop flatpak updating its containers. That might be a working alternative.