Everyone can agree on VLC being the best video player, right? Game developers can agree on it too, since it is a great utility for playing multimedia in games, and/or have a video player included. However, disaster struck; Unity has now banned VLC from the Unity Store, seemingly due to it being under the LGPL license which is a “Violation of section 5.10.4 of the Provider agreement.” This is a contridiction however. According to Martin Finkel in the linked article, “Unity itself, both the Editor and the runtime (which means your shipped game) is already using LGPL dependencies! Unity is built on libraries such as Lame, libiconv, libwebsockets and websockify.js (at least).” Unity is swiftly coming to it’s demise.

Edit: link to Videolan Blog Post: https://mfkl.github.io/2024/01/10/unity-double-oss-standards.html

  • @[email protected]
    link
    fedilink
    English
    846 months ago

    LGPL requires distributing the license with any code. I imagine unity does that with the core code, but it would be difficult to enforce that for assets distributed in their store, which they would be liable for legally. I imagine this will be resolved, but I no longer use Unity so idfc

    • Davel23
      link
      fedilink
      496 months ago

      From my understanding there are other third-party assets in the Unity store which use the LGPL but are not being removed.

      • @[email protected]
        link
        fedilink
        English
        11
        edit-2
        6 months ago

        Is there any information on them being given a pass?

        Generally stuff like this goes in waves. I have no experience with the unity store, but it wouldn’t shock me to find out they haven’t always (and still might not…) required “apps” to list their licensing. Meaning this would be a somewhat manual effort done by a severely reduced staff.

        And I’ll just add on that I expect this to happen to the other “asset” stores. In industry, “GPL is cancer” and “LGPL is herpes”. GPL can straight up “kill” a project and LGPL is usually a mass of headaches that are mostly manageable but can still “cause problems” at times.

    • @[email protected]
      link
      fedilink
      English
      246 months ago

      No it won’t. This is 5.10.4 of the Unity Provider agreement, it’s total bullshit.

      Provider represents and warrants that its Assets shall not contain (a) any software licensed under the GNU General Public License or GNU Library or Lesser General Public License, or any other license with terms that include a requirement to extend such license to any modification or combined work and provide for the distribution of the combined or modified product’s source code upon demand so that Customer content becomes subject to the terms of such license; or (b) any software that is a modification or derivative of any software licensed under the GNU General Public License or Library or Lesser Public License, or any other license with terms similar thereto so that Customer content become subject to the terms of such license.

      • just another devA
        link
        fedilink
        English
        20
        edit-2
        6 months ago

        Why is it bullshit? AFAIK, Unity wouldn’t be able to comply with LGPL without supplying their own source code, so then this would be the only logical outcome.

        • @[email protected]
          link
          fedilink
          English
          25
          edit-2
          6 months ago

          Unity let me go earlier this week, so I’m really not in the mood to defend them, but this is correct. I’m on the Unity hate train as much as the next guy and i feel this is pretty cut and dry.

            • @[email protected]
              link
              fedilink
              English
              176 months ago

              Thankfully I’m in Canada where Collective Layoffs are heavily protected, and I have a generous package to keep me afloat until I find the right job.

              It is a sad week for tech because not everyone has these protections.

          • @[email protected]
            link
            fedilink
            English
            106 months ago

            No, it’s not correct. Unity’s management might think that’s how the LGPL works, but they’re wrong.

            • @[email protected]
              link
              fedilink
              English
              46 months ago

              The fact that they prefer to not do something at all instead of going through the hassle of doing something properly has always been a thing at Unity. It’s correct that it is for business reasons and not necessarily logical ones.

        • @[email protected]
          link
          fedilink
          English
          19
          edit-2
          6 months ago

          You are only required to give source code for changes to that part for LGPL code. So only the library requires that.

          Other game engines supply source code. If Unity wants any hope of redemption they should let us inspect wtf it actually does on our computers (edit: and let us make it work for our needs).

            • @[email protected]
              link
              fedilink
              English
              2
              edit-2
              6 months ago

              Charging for access is actually fine under L/GPL but after that you’re then free to redistribute at your own price. I imagine Unity heavily control how you use and distribute your modified engine (nonfree).

        • @[email protected]
          link
          fedilink
          English
          136 months ago

          Unity uses the LGPL for parts of their own products. The GPL in most cases only requires that derivative work must also be shipped with the same license. The source code from providers doesn’t have to be distributed by unity, it has to be distributed by the provider. In this case that would be videoLAN, which has all their source code on GitHub. You can read the text of the LGPL here, and this is VideoLAN’s post about the situation.

          • @[email protected]
            link
            fedilink
            English
            16 months ago

            The GPL in most cases only requires that derivative work must also be shipped with the same license. The source code from providers doesn’t have to be distributed by unity, it has to be distributed by the provider.

            This is incorrect. The distributor of derivative works in binary form is responsible for providing the source code. They can refer to a server operated by a third party, but if that third party stops providing the source code the distributor remains obligated to ensure that it is still available. The only exception is for binaries which were originally received with a written offer of source code, where the offer can be passed on as-is, but that only applies for “occasional and non-commercial” distribution which wouldn’t work here.

        • @[email protected]
          link
          fedilink
          English
          76 months ago

          I thought the point of the LGPL was to allow this sort of usage without requiring the release of source code. It’s an extension of the GPL to remove those requirements isn’t it?

        • Flying Squid
          link
          fedilink
          English
          16 months ago

          I admit this is totally not my area, but couldn’t you say that about literally any online source that sold software from Steam to the Apple App Store?

    • deadcream
      link
      fedilink
      96 months ago

      Not just license. You also need to link to it as a shared library and allow users to replace it with their own build of the library. Meaning you can’t use stuff like DRM and anticheats.

      • @[email protected]
        link
        fedilink
        English
        56 months ago

        Yup fair point I didn’t know that. Unity presumably does this with dlls that a technical user can easily swap out. In principle an asset store script could do this, but it would be very difficult to verify and enforce so I can see why they’d just ban the license outright as a CYA thing.

        Maybe the answer is to distribute a vlc dll separately and only ship a linking/driving script via the asset store.

    • FaceDeer
      link
      fedilink
      26 months ago

      Not exactly. The LGPL inherits the methods of conveying source code from section 6 of the GPL, which has a number of different options. You can bundle the source code along with the compiled version, but you can also do it simply by including an offer the end user can redeem to get a copy of the source. For example you could include a link to the source code.