4 ms·
Presumably the linux container would be considered an "aggregate", the container as a whole is not a derived work of any of the installed programs. Those are d
by warp 7y ago
Presumably the linux container would be considered an "aggregate", the container as a whole is not a derived work of any of the installed programs. Those are distinct copyrighted works. So you should be fine, and your software would not be covered by the GPL. IANAL.
https://www.gnu.org/licenses/gpl-faq.en.html#MereAggregation https://www.gnu.org/licenses/gpl-faq.en.html#MereAggregation
- mjevans 7y agoIt might be better to think of it like this: A distribution of Linux you happen to use (like Debian) might be entirely freely GPL components. If you ship anything that includes those, you are also required to provide (or at least provide if asked) a copy of the source code, For that Component. If you have a proprietary program that happens to run inside of that Linux distribution, but otherwise does not use GPL/etc sources, that doesn't need to be distributed as such. It's generally better for your customers to not stand in the way of them fixing things/using newer versions of the free upstream, and re-combining in the provided application to form a new version of the whole. That's one of the issues later versions of the GPL tried to address.