> No, that makes no sense. It'd mean that putting two zip files that one > provides > and the other uses a function with the same name next to one another would > make them somehow connected and derivatives of one another. The whole > point of dynamic linking is that you can provide independent implementations > of the API, and you can clearly substitute libcryptsetup with another > implementation, and both bodies of code are usable without one another.
Then how would you interpret the following statements: https://www.gnu.org/licenses/gpl-faq.html#GPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL https://www.gnu.org/licenses/gpl-faq.html#MereAggregation IMHO it's not so obvious and it may depend on a specific case. Perhaps in case of runtime dynamic linking when GPL library existence is not required for the application to run it will be treated as a mere aggregation. With all due respect I think that to solve it we'd need a lawyer indeed :) Krzy _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
