3 ms·
> it would not change the fact that the BSD-licensed component is BSD-licensed. That's correct, as far as I know. But it completely misses the point. I'm not r
by bscphil 5y ago
> it would not change the fact that the BSD-licensed component is BSD-licensed.
That's correct, as far as I know. But it completely misses the point. I'm not required under the BSD to provide anyone with access to the original, BSD licensed code. That's the whole reason people can distribute modified closed source BSD code as they see fit. If I modify a BSD licensed source file and include it in my program, I am free to license the whole thing to anyone as GPL. This does not "change" the licensing of the original component - but I am not providing the original component.
Of course, most of the interest is in going the other direction. If I include a GPL licensed source file in my program, the entire program becomes GPL even if I don't want it to be. Unless the recipient of the software painstakingly removes all GPL components, they must abide by the GPL's requirements for the whole of the software.
- torstenvl 5y ago> But it completely misses the point. No. It does not. As demonstrated by your continued misunderstanding. > I'm not required under the BSD to provide anyone with access to the original, BSD licensed code. True. But I don't think that's relevant to this discussion, as nobody has claimed you had to provide such access. > If I modify a BSD licensed source file and include it in my program, I am free to license the whole thing to anyone as GPL. No, you are not. Nothing in copyright law or the BSD license allows you to do so (again, probably, unless a court in the future expands the idea of a "compilation" to software). > This does not "change" the licensing of the original component - but I am not providing the original component. Your modified file would still have a big ol' BSD license attached to it, unless you violate the BSD license by removing it. What exactly is your plan for convincing a judge that you really licensed that file under the GPL despite publishing it with a BSD license statement? > If I include a GPL licensed source file in my program, the entire program becomes GPL even if I don't want it to be. Um. No. It's hard to figure out what confusion of ideas could possibly lead someone to this conclusion. > Unless the recipient of the software painstakingly removes all GPL components, they must abide by the GPL's requirements for the whole of the software. Abjectly false. There is no requirement to abide by the GPL for a work that is licensed under the BSD license, and there is also no possibility of changing it so that such a component is not BSD-licensed.
- bscphil 5y agoYou're being so absurdly rude that I refuse to continue this conversation with you any further. I only suggest, for the sake of anyone who followed this conversation for its intellectual interest, that you provide some kind of argument for your views rather than just claiming repeatedly to be very right.
- deleted 5y ago[deleted]
- dpark 5y ago> I am free to license the whole thing to anyone as GPL. This is what you’re getting wrong. You can “distribute GPL software that includes BSD components” but this is a misstatement of what actually happens. You are distributing your own software as GPL code and at the same time distributing the BSD components. The license to those components (or their source code) does not change. You absolutely can’t blanket apply the GPL to the whole thing. > This does not "change" the licensing of the original component - but I am not providing the original component. You absolutely are. If I ship a book full of Sci Fi stories I wrote, and happen to include some classic Philip K Dick stories, I have absolutely included the original. The fact that I wrapped it in my own work changes nothing.