On Tue, Jul 18, 2017 at 10:13 AM, Bastien Nocera <had...@hadess.net> wrote: > That's fine. The license of the compound work just has to be compatible > with the individual files' licenses, it doesn't need to be the exact > same one. > For example, you can have a project mixing GPLv2+, GPLv3+ and BSD > licensed files, and choose to have the compound work be GPLv3+. That > also tells contributors that any new files in the project should be > compatible with that overall license.
I’m not claiming it doesn’t work. I’m just pointing it effectively means the files haven’t switched licenses, which is what was intended. nautilus-main.c and others still are under GPLv2+ and one can use them under GPLv2 if they so choose. -- Alexandre Franke GNOME Hacker & Foundation Director _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
