We are using Qt(5.3.2 - opensource) for one of our applications that we are going to be distributing (closed-source). We dynamically link to Qt and have made no modifications to Qt.
At Qt's Legal FAQ, they list the necessary obligations for using Qt under the LGPL. We understand and agree with their interpretation of the LGPL for all of their points except the first one,
... You will need to deliver the complete source code of Qt (including all modifications you did or applied) to your users/customers. Alternatively you need to provide a written offer with instructions on how to get the source code. Please also note that this has to be under your control, so a link to the source code provided by the Qt Project or Qt Company is not sufficient...
Is this correct by LGPLv3 standards? I need to have my own host of the library's code even when there are no modifications? I cannot just point my license statement to an already hosted location?
Every single application that has ever used Qt, dynamically linked without modifications, has to have a separate storage/distribution of the libraries source code?
If this is truly necessary, Is my assumption that pointing to a clone of their git repository (hosted on Github/Bitbucket/etc...) would be enough to satisfy this requirement?
Lets say I do self-host my applications code (open-source for this clarification) and my LGPL dependencies (as said in the FAQ). If someone else wanted to now use my code and redistribute their modifications, they wouldn't know that they needed to self-host the dependencies as it's not written in the license but only on the dependencies websites FAQ which isn't being distributed with their source!
Yes, you might fall victim to an issue of the original source location being removed, but the GPL states that you must make it available upon written request, which you should be able to do if/when the original location no longer hosts it and someone wants it specifically from you.
The title might have Qt in it, but the question is broader. The license doesn't require self-hosting and as a result most (prove me wrong, please!) projects do not self-host.