The GPLv3 allows free distribution and DOES NOT LIMIT distribution of binaries
except that source must be distributed at the same time.
You claim to have other restrictions - not free for commercial use or some
other harm.
The two are not compatible.
FullFAT is EITHER covered by the GPLv3 - which says you cannot modify, add, or
remove restrictions (and you do include the full text). OR it is non-free
software with the restrictions you impose.
Which is it?
If you wish to have the restrictions, you should remove the GPLv3 licensing
assuming you have not already lost the right to prohibit distribution under the
GPLv3 including for commercial use. Check with a lawyer, but I'm just pointing
out that it is an either-or decision. It CANNOT be GPLv3 yet restricted to
non-commercial use or anything else not covered by section 7.
http://www.gnu.org/licenses/gpl-faq.html#NoMilitary quote:
(q) I'd like to license my code under the GPL, but I'd also like to make it
clear that it can't be used for military and/or commercial uses. Can I do this?
(a) No, because those two goals contradict each other. The GNU GPL is designed
specifically to prevent the addition of further restrictions. GPLv3 allows a
very limited set of them, in section 7, but any other added restriction can be
removed by the user.
From section 7 of the license:
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term.
From section 10:
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License,
Original issue reported on code.google.com by tz2026 on 27 Mar 2014 at 4:58
Original issue reported on code.google.com by
tz2026on 27 Mar 2014 at 4:58