Re: [OF] where to put license files?

[Mike Miller]

On Wed, Dec 23, 2015 at 22:36:16 +0100, Philip Nienhuis wrote:
> 
> Carnë Draug wrote:
> >You leave your COPYING file with the GPLv3+ license and simply add the
> >file under the MIT license to the repository.
> 
> My very question was *how* to do that. If I simply put it anywhere in the
> package, it never gets installed.
> 
> Anyway I saw that that same MIT license text is already in the .cc file so
> the my question is a bit moot.

Yes, I think that's the best solution. The MIT/Expat license is so short
it can fit in the file header in its entirety, while the GPLv3 cannot.

Alternatively you could ship a COPYING.MIT alongside COPYING. It may not
be installed into packinfo, but that's the right place for it if
anything.

> >However, since you are modifying the code, you can put your changes under
> >the GPL.  In that case, just add the GPL header to the top of the file
> >followed by:
> 
> I'd be equally happy with adding my modifications under that same MIT
> license. That MIT license is GPL-compatible, after all.

Either approach works IMHO. The overall license of the mapping package
will be GPLv3+ (that's what I would put in DESCRIPTION), every compiled
.oct file will be GPLv3+, even if all of its sources are MIT, but each
file may be under its own individual license.

-- 
mike