4 ms·
I spent some time reading about static linking and dynamic linking. From the FAQ > "Linking a GPL covered work statically or dynamically with other modules
by jay_kyburz 2y ago
I spent some time reading about static linking and dynamic linking. From the FAQ
> "Linking a GPL covered work statically or dynamically with other modules is making a combined work based on the GPL covered work. Thus, the terms and conditions of the GNU General Public License cover the whole combination"
If I had to guess, if you installed each application in your stack separately, and they simply interacted with each other through API calls, you could consider them "System Libraries" and therefore would not dragged into the AGPL. Example, The OS itself, Node, Postgres, and any other 3rd party applications. As long as you are not distributing them, I think they would count as System Libraries.
> "To prevent unscrupulous distributors from trying to use the System Library exception as a loophole, the GPL says that libraries can only qualify as System Libraries as long as they're not distributed with the program itself. If you distribute the DLLs with the program, they won't be eligible for this exception anymore"
- wavemode 2y agoThe System Library exception isn't even needed. The key word in what you've quoted is "linking". If you aren't linking, then you aren't creating a combined derivative work at all. Linking in this context refers to a very specific thing: https://en.wikipedia.org/wiki/Linker_(computing) https://en.wikipedia.org/wiki/Linker_(computing)