I don't know of an example, but yes you are correct. I don't think the LGPL specifies the exact means that the software should be published in. EPL has a similar requirement for publishing the source code if you have modified their stuff, and I have heard that a standard thing for IBM to do for example is have a zip file of the sources available somewhere on their site or with the product distribution.
So long as it's clear where to find the source, I don't think it matters much exactly how you publish it. And if you have not modified the LGPL source, then you can refer to some place where it is published. You only need to actually publish it if you have modified it in some way (or its not published elsewhere).
发布评论
评论（1）
我不知道有什么例子，但是你是对的。我不认为 LGPL 指定了软件应该发布的确切方式。如果您修改了他们的内容，EPL 对发布源代码有类似的要求，并且我听说 IBM 的标准做法是在其网站上或产品发行版上有一个可用源的 zip 文件。
只要清楚在哪里可以找到来源，我认为如何发布它并不重要。如果您没有修改 LGPL 源代码，那么您可以参考发布它的某个地方。仅当您以某种方式对其进行了修改（或者未在其他地方发布）时，您才需要实际发布它。
I don't know of an example, but yes you are correct. I don't think the LGPL specifies the exact means that the software should be published in. EPL has a similar requirement for publishing the source code if you have modified their stuff, and I have heard that a standard thing for IBM to do for example is have a zip file of the sources available somewhere on their site or with the product distribution.
So long as it's clear where to find the source, I don't think it matters much exactly how you publish it. And if you have not modified the LGPL source, then you can refer to some place where it is published. You only need to actually publish it if you have modified it in some way (or its not published elsewhere).