• [deleted]

  • Post #21

retrowertz No, where did you get that thought?

    The goal is to fully deprecate 3rd-Party, however for specific applications like Chrome where there is neither an officially-supported flatpak nor a snap, those will use the current legacy system.

      JoshStrobl
      Getting rid of that devoted page will be heartbreaking (I've come to know it and love it) but I know you guys and girls are aiming at streamlining.
      Will these 3rd party apps be transferred to the 3rd Party tab in Software Center? Or will these current things be exclusively Snap? Or undecided?
      WIll they be maintained by you or independent of you? Or the way it is now: maintained but with the "install at your own risk" disclaimer you have in the SC?
      So many questions, sorry!

        1. Snaps and Flatpaks are likely going to be integrated into our existing category system, with an indication that it is a snap or flatpak, and not something that is from the repo (or a disclaimer along those lines). The same goes for any 3rd-Party applications (namely Chrome and its various channels), which will have appropriate disclaimers as well.
        2. 3rd-Party is already maintained by us. We are not committed to providing any snaps or flatpaks, that is the responsibility of the software vendor / developer to do. If we're not allowed to redistribute it (we're explicitly permitted to do so with Discord, Teamspeak, Vivaldi to name a few) then the vendor has to provide it themselves.
        3. Only very specific cases like Chrome will warrant the use of our legacy 3rd-Party repo, everything else will be removed. So the expectation would be for say, GitKraken, that you would install it via snap instead of 3rd-Party, or same with Spotify, and as such we would remove it from our legacy repo.
          2 years later