multiple sub-programs, multiple licenses, one package?

[Ralf Corsepius]

On Thu, 2005-08-25 at 10:11 +0200, Nils Philippsen wrote:

> I'd call using "Distributable" in the case of multiple licenses
> chickening out. "Read the licenses for yourself" would be more honest.
> I've yet to come over something that has more than 3 licenses in one
> package
Well, many OSS packages of considerable size and with a long history
have "many licenses". A master piece is newlib.

Try building a newlib based cross GCC toolchain (e.g. Cygwin cross
toolchain). Newlib has different licenses in almost each file.

>  and I think we should mention them all in the License: field, if
> needed having MANIFEST.${LICENSE} files that state what part/file is
> covered by which license in the documentation.
That won't work for "many licenses" cases.

Also consider that a spec's License:-field probably isn't legally
binding and probably is "just informative".

IMO, the only point that matter there is "not to lie" at users. This
would mean, using "Distributable" or "OSI-compliant" for "many licenses"
would be fine with me.

Ralf