> > Not strictly true. They can either agree to a change and issue one or
> > they can convey to other parties the right to change the terms. The GPL
> > for example does this for version selection.
>
> So, under a dual-licensed BSD/GPL code the latter license allows a
> developer to remove the GPL license itself and release a single-licensed
> BSD code if other parties want to do it?
If the dual licence permits you to select from two alternatives as
appears to be the case in
"* Alternatively, this software may be distributed under the terms of the
* GNU General Public License ("GPL") version 2 as published by the Free
* Software Foundation."
Then there is no problem in doing exactly what it says and distributing
it under the terms of the GPL v2 and the GPL v2 alone (or indeed the BSD
licence alone). Anyone who took the project code and produced a binary
only proprietary product from it would for example select the BSD licence
alone and convey almost no rights at all to their customer.
> I would assume a file as a boundary of a work in the case that file is
> under different licensing terms to the rest of the software package. On a
Assuming is bad, you should consult caselaw.
> lot of software packages different modules are covered under different
> licensing terms.
>
> We can choose what license terms we will honor; however, we do not have
> the ability to remove the licensing terms we do not like.
If the author has conveyed that right to you, then you may usually do so.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
