News for hackers. Stuff that matters.
Re:LLVM relicensing update and call for help by dagmx on Sunday November 21, 2021 @12:30AM (#29294407)
Out of curiosity, how does the GPL promise that versus the other common open source licenses? E.g MIT, BSD or Apache?
Re:LLVM relicensing update and call for help by purple_turtle on Sunday November 21, 2021 @01:16AM (#29294552)
As I understand it:

MIT code can be freely taken into proprietary fork, with software modified and sold and no patches contributed.

Not sure how often it happens? Has it actually happened and is it a plausible attack? Nowadays at least AGPL is needed to defang "and we will sell it as service rather than selling software" workaround for GPL.

Re:LLVM relicensing update and call for help by pjmlp on Sunday November 21, 2021 @04:25AM (#29295124)
Apple derived OSes, the Windows TCP/IP stack before Windows Vista, PlayStation OSes, Nintendo and Playstation SDK, the BSD stuff taken into commercial UNIXes, just from top of my head, there are surely other examples.
Re:LLVM relicensing update and call for help by arka2147483647 on Sunday November 21, 2021 @03:12AM (#29294911)
As a practical matter, it means you cant just copy the files into your sources to some subdir, or you cant just link it statically. So you cant release a single-exe version of your project.

These are things some projects like to do, and GPL blocks that. So all thing considered, it may be easiest to just not use GPL code.

Re:LLVM relicensing update and call for help by chayleaf on Sunday November 21, 2021 @03:36AM (#29294978)
you can't copy MIT-licensed files without crediting it either.

And you can statically link GPL code, assuming you release the source to all app users. You might be confusing it with LGPL, which says you can link to proprietary apps dynamically, but have to release source in all other cases.

Re:LLVM relicensing update and call for help by shoozza on Sunday November 21, 2021 @04:14AM (#29295092)
You can also link to proprietary apps statically if you provide the object files: https://softwareengineering.stackexchange.com/questions/3127...
Re:LLVM relicensing update and call for help by rocqua on Sunday November 21, 2021 @04:18AM (#29295106)
I thought useing GPL code without modifications was acceptable without any licensing, or is that a 'lesser GPL' license?
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @04:40AM (#29295173)
You can use GPL code however you want.

You have only obligations when you distribute the results. Whatever you do in your private basement is completely unaffected by that. The GPL gives you freedom to do whatever you please. That's the whole point of it!

When you distribute binaries resulting form work based on GPL code than the people receiving those binaries (and only them) are eligible to get alongside the source code which allows them to rebuild the binaries you distributed to them. That makes sure that those other people also have the same freedom as you to do whatever they please with the programs and code. So the GPL preserves freedom among users of GPL code.

Re:LLVM relicensing update and call for help by orra on Sunday November 21, 2021 @04:25AM (#29295125)
You're thinking on the LGPL.

The GPL is the prototypical copyleft licence, designed to encourage the liberation of software, in part via its dependencies.

Re:LLVM relicensing update and call for help by rocqua on Sunday November 21, 2021 @04:07AM (#29295077)
Apple's OS is a fork of BSD without the fork being open source.
Re:LLVM relicensing update and call for help by kergonath on Sunday November 21, 2021 @04:35AM (#29295157)
It’s more complicated than that. It was not a fork, they just copied some parts of FreeBSD and OpenBSD. The kernel is XNU, and descended from Mach. Also, Darwin (the base OS, which includes the BSD bits) is open source. What isn’t is the GUI on top of it, which comes from OPENSTEP.
Re:LLVM relicensing update and call for help by chalst on Sunday November 21, 2021 @07:05AM (#29295773)
The open source part of Darwin/XNU doesn't deserve to be called a "base OS" since version 6, when Apple closed the sources of a lot of drivers. There's no hardware that will boot these systems if you restrict to what is available under the APSL.

https://web.archive.org/web/20091118172944/http://www.pureda...

Re:LLVM relicensing update and call for help by TravelPiglet on Sunday November 21, 2021 @04:38AM (#29295167)
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @01:20AM (#29294562)
GPL software, and extensions to it, are free and will stay like that.

That can't be said about software under the above mentioned licenses.

Re:LLVM relicensing update and call for help by dagmx on Sunday November 21, 2021 @01:29AM (#29294589)
I'm not sure how the GPL guarantees that it will stay like that anymore than those other licenses?

You can always relicense GPL content as long as everyone agrees. You can also change it to source on request versus always accessible.

Re:LLVM relicensing update and call for help by rocqua on Sunday November 21, 2021 @04:19AM (#29295109)
If you wrote the code, you can refuse to relicense.
Re:LLVM relicensing update and call for help by chayleaf on Sunday November 21, 2021 @03:37AM (#29294985)
key is "as long as everyone agrees"
Re:LLVM relicensing update and call for help by kitd on Sunday November 21, 2021 @03:13AM (#29294918)
OP also said it was a sign of 'quality'. Not sure how GPL promises that over other OS licenses.
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @04:17AM (#29295100)
I'm the OP and I'm not a native speaker but to my knowledge "quality" denotes in English besides a few other things the meaning of "value" (in the sense of worthiness) or (related to that meaning) "excellence". Something being high-quality makes this thing valuable.

I didn't mean "code quality", or the like, as a license can not enforce that obviously.