Earlier quoted context omitted.
This is kind of the crux of a long history of these licensing arguments. That dynamic linking is problematic because it potentially creates a derived work. And then you might distribute that derived work. But shelling out to something or in some cases having an automated script create or download the derived work automatically is sometimes acceptable. It’s a bit of a silly line in some ways. But it’s a long story.
I'm skeptical that there's a coherent legal distinction to be drawn between using a dynamic library with dlopen etc and running a similar executable with arguments. It's functionally identical usage of some public interface.
60x speed-up of Linux “perf”
101–110 of 224 posts
Re: 60x speed-up of Linux “perf”
#102It is a tough feeling to see someone else's design for a library that would be literally perfect for my needs, but I'm unable to use it because of the license, so I have to spend weeks implementing my own inferior version while carefully avoiding making the code too similar to what I happen to remember. I'm past believing that I'm smart enough to always be able to come up with/reimplement a competent enough solution…
This is the comment that points out the issue. perf is licensed under GPL v2 only and libbfd is a GNU tool that is licensed GPL v3 and higher. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911815 Really wish the Linux kernel would start mandating new patches to be GPL v2 and higher and get buy in from the largest contributors. A decade later new code would like replace the smaller contributors code and we could c…
Since, realistically, neither Linux nor GNU will budge, maybe the practical solution would be to look into integrating with the equivalent library in the LLVM ecosystem (assuming it exists).
Re: 60x speed-up of Linux “perf”
#103Earlier quoted context omitted.
IMO it's not "GPL virality" that is at the root of the issue here. The authors' decision to license theis works this way causes the problem. You can still ask both libraries' authors for relicensing their work in a less restricted / more compatible way. If they don't want to do that, then being authors and owning their copyrights, that's their right to do. That's nothing I would blame on the GPL. I mean we should be…
> The authors' decision to license theis works this way causes the problem. I'm not sure how you can rationally make an argument for a framework that literally limits the use of improved or more performant code/technology/understanding simply because it does not share a philosophical view of IP/ownership/sharing. This is the core of the problem with IP in the real world as well, and I find it mind-boggling that we do…
Re: 60x speed-up of Linux “perf”
#104FINALLY AN ACTUAL ANSWER!! :D I had done a bunch of research into this a while ago and filed an issue with the Ubuntu bug tracker, but was told it was due to ABI stability (which did not make any sense). https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894407 Understanding that there is actually an underlying license problem is like finally being told all of the reasons for everything that happened on LOST ;P.
Re: 60x speed-up of Linux “perf”
#105Earlier quoted context omitted.
This is kind of the crux of a long history of these licensing arguments. That dynamic linking is problematic because it potentially creates a derived work. And then you might distribute that derived work. But shelling out to something or in some cases having an automated script create or download the derived work automatically is sometimes acceptable. It’s a bit of a silly line in some ways. But it’s a long story.
I'm skeptical that there's a coherent legal distinction to be drawn between using a dynamic library with dlopen etc and running a similar executable with arguments. It's functionally identical usage of some public interface.
Re: 60x speed-up of Linux “perf”
#106Earlier quoted context omitted.
The thing is with GPL you have to contribute back, see how much Linux has grown in functionalities and how backwards are other kernels with MIT --- You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable so…
But companies wouldn't use it anyway since it's GPL. Enter MPLv2, with the best of both worlds: - not viral copyleft - but users DO have to contribute back
So in that sense it's only very marginally 'better' than a fully permissive license.
Re: 60x speed-up of Linux “perf”
#107Earlier quoted context omitted.
I'm skeptical that there's a coherent legal distinction to be drawn between using a dynamic library with dlopen etc and running a similar executable with arguments. It's functionally identical usage of some public interface.
They don't seem to claim there is a distinction on the mechanics there? Rather their distinction seems to be "are these part of the same overall program, or two separate ones", however you measure that: https://www.gnu.org/licenses/gpl-faq.html#GPLPlugins
Re: 60x speed-up of Linux “perf”
#108Earlier quoted context omitted.
I guess MIT and Apache would be better, so that company can make billions on the code and contributors would still be poor (see AAPL -> FreeBSD)
Right, and GPL is making all of us open source devs rich. I can't fathom getting into open source and then getting mad when people use your tools to great success.
Re: 60x speed-up of Linux “perf”
#109It is a tough feeling to see someone else's design for a library that would be literally perfect for my needs, but I'm unable to use it because of the license, so I have to spend weeks implementing my own inferior version while carefully avoiding making the code too similar to what I happen to remember. I'm past believing that I'm smart enough to always be able to come up with/reimplement a competent enough solution…
Re: 60x speed-up of Linux “perf”
#110Yet another case of GPL virality causing more issues than it solves. E: Downvoters, have you read the article? The program started a new process for each address lookup instead of using a library because that library is GPL. Shall we have a discussion?
IMO it's not "GPL virality" that is at the root of the issue here. The authors' decision to license theis works this way causes the problem. You can still ask both libraries' authors for relicensing their work in a less restricted / more compatible way. If they don't want to do that, then being authors and owning their copyrights, that's their right to do. That's nothing I would blame on the GPL. I mean we should be…