Hi Martin,
We /can/ include GPLv3 code, but not remain GPLv2+ only. there's a whole section on the SFLC website about keeping multiple licenses within the same project.
Yeah, but why all the effort of getting approval from authors of GPL3 licensed files in Inkscape's codebase to publish them as GPLv2+ instead if we now start to include GPLv3 code again?
Also this was what you told me when I wanted to include Scour (which uses the Apache license and would actually have been allowed in a GPLv3 (not v2 though) project:
Am 27.11.2015 um 03:39 schrieb Martin Owens:
I do worry about the licensing issue a bit. It's not too much of a problem for our windows or mac builds, but our debian package is single licensed and they tend not liking mixed packages. i.e. it should be in it's own repository and package.
Either way: It won't help solve the initial problem (Neither GPLv2 nor GPLv3 can be included in Apache code), but I don't think there is any problem as long as Nicolas is fine with dual-licensing... As I wrote before: I doesn't have any downsides I'm aware of.
Regards Eduard