In case I would dynamically link to a LGPL-licensed library (in this case Qt) in a commercial application: Which way do I have to provide the library's source code?
- Is a link to the project homepage sufficient? Or would I need to host the source code on our servers? For which period of time after distribution of the software would this website need to be kept up? (or would "on request" be also compliant with the LGPL?)
- Is it still necessary to offer the source code in a physical way (e.g. on CD via snail mail) for 3 years (any difference between
I've found this in the GNU FAQ:
Can I put the binaries on my Internet server and put the source on a different Internet site?
Yes. Section 6(d) allows this. However, you must provide clear instructions people can follow to obtain the source, and you must take care to make sure that the source remains available for as long as you distribute the object code.
I've highlighted the relevant part as bold text. However, I cannot believe, that this is the complete truth. If I distribute an application only once, then I could put the source code online and take it down a day later. So this still doesn't answer my question...
There is another question with a related topic here, but it has a different attempt than mine. It only asks for alternatives to shipping the source code directly with the binaries, while my question aims to clarify which circumstances and conditions I would have to consider / respect when sharing the LGPL library source code.