Announcement

Collapse
No announcement yet.

Mir Display Server Lands API Changes, Relicenses Headers To LGPL

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mir Display Server Lands API Changes, Relicenses Headers To LGPL

    Phoronix: Mir Display Server Lands API Changes, Relicenses Headers To LGPL

    Canonical's Mir developers are working to get Mir 1.0 released in 2017 and in preparation for that stable milestone they have just landed a number of API changes...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    All right, haters. You lot better pile in here and dis Mir. It's showing signs of progress, and we can't have that, now can we?

    Comment


    • #3
      Originally posted by wswartzendruber View Post
      All right, haters. You lot better pile in here and dis Mir. It's showing signs of progress, and we can't have that, now can we?
      No need. Canonical can make a mockery of things all on their own, no assistance required...

      Comment


      • #4
        Originally posted by Delgarde View Post

        No need. Canonical can make a mockery of things all on their own, no assistance required...
        IMHO they already did just that when they chose to release their specs into an obscure version management system.
        They could probably gather more widespread support just by switching to git or hg.

        Comment


        • #5
          Why would someone change licence on just the headers, as it seems the some of the code is either gpl3 or lgpl (or maybe something else in some places).

          This is a bit confusing, how does that legally work?

          Comment


          • #6
            Originally posted by yoshi314 View Post
            Why would someone change licence on just the headers, as it seems the some of the code is either gpl3 or lgpl (or maybe something else in some places).

            This is a bit confusing, how does that legally work?
            Because others would need to include the headers in there code if they where to write something that directly interacts with Mir. So the license needs to be able to coexist with other licenses.

            Comment


            • #7
              I was always baffled that Mir was in GPL instead of LGPL. I love free software, I'd love for all software in the world to be GPL-licensed. But that's not the world we live in, and it seems crazy to force people that might want to use Apache license, BSD license, EPL, MIT, MPL, etc.... to be forced to switch to GPL or avoid using Mir.

              Comment


              • #8
                Originally posted by wswartzendruber View Post
                All right, haters. You lot better pile in here and dis Mir. It's showing signs of progress, and we can't have that, now can we?
                you got it!

                Canonical's Mir developers are working to get Mir 1.0
                $ pacman -Q wayland
                wayland 1.12.0-1

                An anonymous reader writes: Fedora 25 will finally be the first release for this Linux distribution -- and the first tier-one desktop Linux OS at large -- that is going ahead and using Wayland by default. Wayland has been talked about for years as a replacement to the xorg-server and finally with th...


                You know, instead of being special snowflakes, Ubuntu could actually contribute to shit other people use. That would be nice.

                Comment


                • #9
                  wow i booted live cd of Ubuntu 17.04 (Zesty Zapus) Daily Build with Unity8 and it sometimes looks more broken than Wayland on Gnome but at least there is native mir chromium based browser and some nice polished tablet friendly user interface, memory usage is also much better. The whole thing crashed after hitting PrintScreen key.

                  Comment


                  • #10
                    Originally posted by yoshi314 View Post
                    Why would someone change licence on just the headers
                    to allow inline functions in headers without forcing users to gpl3. but now you can't freely move code between header and source, lol

                    Comment

                    Working...
                    X