Re: BSD & MIT licenses compatible?
Joe Smith wrote:
> "Suraj N. Kurapati" wrote:
>> So when I appended bsd.c to mit.c, did the entire mit.c become
>> licensed under both licenses? That is, did the originally-MIT
>> portions of mit.c inherit the extra condition from the BSD
> That is an easy way to view it. Technically, what you had said
> before is perfectly correct, but thinking of the file as being
> licenced under the combination of the conditions is also
> perfectly valid (as long as you realize that if the parts are
> seperated, the original lices still apply, of course).
> In summary, just make sure you meet all the terms of both, and
> you are fine.
To further my understanding, please consider the following:
Suppose that you take the original, pure versions of mit.c and bsd.c
and combine them into a combined.c file, like this:
cat mit.c bsd.c > combined.c
After receiving the combined.c file from me, you make some
modifications and save the file as combined1.c
1. When you redistribute combined1.c, you have a choice of placing
the modifications under either BSD or MIT license, but not both.
2. Whoever receives combined1.c from you still has the ability to
extract the new (including your modifications) BSD or MIT portions.
The pattern I am seeing here is: "united we stand, divided we fall"
[united we stand]: When we distribute a bunch of code, the
conditions of all licenses that apply to that code must be satisfied.
[divided we fall]: Once a person obtains the distribution and
extracts the files, the code is once again separate (i.e. different
files/portions of the code remain under different licenses -- as if
So the special case (application of conditions from all licenses)
only applies during distribution.
Is this correct?
Thanks for your consideration.