We plan to ship an application together with the required dynamic-libraries (SO/DLL), we link dynamically against one of these libraries, which uses the others libraries.
The LGPL requires us to provide the libraries-sources. I assume I can provide the sources in a second package from our server, servers of the original projects or using the possibility to offer the code for three years (see Section 6, GPL). At the moment I tend to use that three year clause from Section 6, Paragraph B of the GPL. Because literally nobody will replace the libraries and if they want, the will likely use newer versions of the library which we don't use. Furthermore, we don't have to maintain the downloads on ourselves, just keep a backup of the library-sources.
- Is that correct?
- Do you now a good example of a closed-source application, which comes together with LGPL-Libraries?
I thought about looking at libflashplayer, but that is a bad example. Adobe just includes a copyright notice and the LGPL. Which is probably okay, because they don't deliver the LGPL-Libraries on their own and assume they are available. I can't, because we target also Windows and have to provide our stuff in a complete package. Thankfully we can build our work on the libraries and the LGPL, but it is weirdly written.
I originally asked this question on Stack Overflow, but wasn't able to move it here, so I opened here this question again.
We're linking against libmicrohttpd* which is using the LGPLv2.1 or at option any later version. Furthermore we running the executable on a regular IBM compatible personal-computer and not shipping it on a device or appliance. As far as I know, we are not building up on any patented-stuff.
*I can really recommend this project, the people are helpful and friendly. I should spend some euros for them.