On Sun, Mar 20, 2016 at 12:04:12PM +0300, Alexander Inyukhin wrote: > On Sun, Mar 20, 2016 at 05:40:59AM +0000, Mattia Rizzolo wrote: > > and btw, having debian/* GPL-2+ technically makes upstream unable to > > pull patches from debian/patches/*, as GPL-2+ is incompatible with > > GPL-2 (only).
This is incorrect. GPL-2 and GPL-2+ are compatible, both ways, with the combined result being effectively GPL-2 but anyone can still pick GPL-2+ parts and use them under GPL-2, GPL-3, GPL-4, GPL-4636467912 and, unfortunately, AGPL-3 (which I consider a non-free license). > Isn't that a one-way incompatibility? > As far as I understand, GPL2+ is a set of licenses including GPL2, > so GPL2+ code could be used in GPL2-only project. So can GPL2-only code be used in a GPL2+ project (at the cost of restricting the result to GPL2-only). > Anyway, I do not want to restrict use of these patches. > What license should I use? GPL-2+ as you currently do. This way upstream can use your patches now, and will continue to be able even if they relicense to a higher version of GPL in the future. -- A tit a day keeps the vet away.
