On Apr 6, 4:27 pm, allan <allan1...@gmail.com> wrote:
> LGPL/GPL have the obligation to provide source with any binary
> distributions. Source can be provided directly with the binaries or in
> an offer, made available to the public for 3 years.
No, this is true of works using the GPL, but not of works using the
LGPL.
>
> You cannot fulfill the obligation by pointing to a 3rd party download
> site for the source. Go ask Cisco and others who have had to comply
> with this requirement.
The LGPL does not require source, it is only one of a myriad of
options to comply with it.
>
> GWT/Google provides neither an offer or the source.
As they don't have to
>
> Not only is Google in violation but I, or any one redistributing GWT,
> will be violating LGPL as well. I will have to separately provide the
> source any time I distribute GWT.
No, you aren't.
>
> GWT package should include the source code for any LGPL components.
>
It doesn't have to.
If GWT was modifying the LGPL works, it would need to comply with
other sections of the LGPL, but as it simply "uses" the works
unmodified, it is only required to comply with section 6.
See section 6 of LGPL 2.1 (which is the license for the LGPL
components of GWT):
"6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a work
containing portions of the Library, and distribute that work under
terms of your choice, provided that the terms permit modification of
the work for the customer's own use and reverse engineering for
debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
...
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a copy
of the library already present on the user's computer system, rather
than copying library functions into the executable, and (2) will
operate properly with a modified version of the library, if the user
installs one, as long as the modified version is interface-compatible
with the version that the work was made with.
"
As GWT complies with section 6 (and is a work that uses the library),
using option b (note it says "you must do one of these things, not all
of these things"), there is no requirement they make an offer for
source.
HTH,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
