object code distribution requirements in GPLv2 and GPLv3
Posted Jul 12, 2007 8:54 UTC (Thu) by
dark (
✭ supporter ✭, #8483)
In reply to:
object code distribution requirements in GPLv2 and GPLv3 by JesseW
Parent article:
An update on Yoggie GPL compliance
The GPLv3 is too new for me to comment on, since I haven't studied it
thoroughly, but I'd like to focus on the wording of clause 3(b) of the
GPLv2:
Accompany it with a written offer [...] to give any third
party ...
Notice that it's not just an offer that is valid for any third
party.
It must be an offer to supply the source to any third party. If I
get such
an offer, and then they refuse to supply the source to any third party,
then they didn't honor the offer they made to me.
As a reminder, I'd like to point out that such an offer doesn't have to
be a
physical token. It must be "written", but it could be written on a web
page or inside an iso9660 image. This is
illlustrated by clause 3(c),
which says:
Accompany it with the information you received as to the
offer ...
So, it doesn't talk about passing on the offer or making copies of the
offer. Information
about the offer is sufficient. This makes sense if the original
offer was already to supply source to any third party. Then knowing about
the offer is just as good as having a "copy", whatever that means exactly.
One detail that's always amused me is that the GPLv2 does not actually say
that you have to honor these offers :) It's not clear to me who would have
standing to sue if you don't.
(
Log in to post comments)