asaf gil
2012-09-03 21:21:23 UTC
I believe that an application constructed as you describe would
count as a "Combined Work" under the LGPL, so you'd have to do
the five things described in part 4 of the current LGPL (online
at http://www.gnu.org/licenses/lgpl.html ). Your script would
probably satisfy requirement 4d1, and requirement 4e probably
doesn't apply to you or is already satisfied by your installation
documentation, so I think it would be enough for you to change
your documentation to satisfy parts 4a, 4b, and 4c.
....count as a "Combined Work" under the LGPL, so you'd have to do
the five things described in part 4 of the current LGPL (online
at http://www.gnu.org/licenses/lgpl.html ). Your script would
probably satisfy requirement 4d1, and requirement 4e probably
doesn't apply to you or is already satisfied by your installation
documentation, so I think it would be enough for you to change
your documentation to satisfy parts 4a, 4b, and 4c.
As to the license, it seems that if I would follow the requirement 4d1
and if the requirement 4e applied to me, I would have to also "convey
Corresponding Source". Trying to find out whether I have to provide
such information leads to a down spiral through the GPL.
Isn't Sassy distributed under LGPLv2.1 rather than v3? There's noand if the requirement 4e applied to me, I would have to also "convey
Corresponding Source". Trying to find out whether I have to provide
such information leads to a down spiral through the GPL.
"Corresponding
SourceĀ clause in that version.
Asaf