4 ms·
LLVM is considering switching to the Apache 2.0 License. As a matter of policy, OpenBSD does not ship software that uses the Apache 2.0 License. It's not enti
by maxerickson 10y ago
LLVM is considering switching to the Apache 2.0 License.
As a matter of policy, OpenBSD does not ship software that uses the Apache 2.0 License.
It's not entirely clear why that is their policy, but it seems to come down to some combination of the patent clause and the additional complexity of the license.
- teamhappy 10y ago> It's not entirely clear why that is their policy > The original Apache license was similar to the Berkeley license, but source code published under version 2 of the Apache license is subject to additional restrictions and cannot be included into OpenBSD. (http://www.openbsd.org/policy.html http://www.openbsd.org/policy.html)
- maxerickson 10y agoRight, which is clear as mud and not really an explanation. It's roughly equivalent to just saying they don't like the license.
- teamhappy 10y agoAccording to the link I posted their goal is to publish OpenBSD under the terms of the original BSD license (so 2-Clause BSD, 3-Clause BSD, MIT, ISC, etc. are all fine). The Apache license v2 is more restrictive than BSD-style licenses so they can't include code licensed under it.
- michaelmrose 10y agoIts not clear that there is any legal restriction on them doing so.
- teamhappy 10y agoIn the sense that it would be perfectly legal for them to include Apache v2 licensed code? What in the world would restrict them from doing so? They can include Apache v2 code, GPLed code, proprietary code, any code they want, really. Their goal however is to build an OS that can be used under the terms of a BSD-style license similar to Debian's goal to build an OS that is "free."
- eridius 10y agoBut if they're already shipping GPLv2 code then they've already failed at this goal.
- deleted 10y ago[deleted]