4 ms·
Wow, really? So it’s essentially impossible to use this for proprietary software? I knew about the server stuff, but I didn’t think the AGPL bound compiled prog
by OskarS 7y ago
Wow, really? So it’s essentially impossible to use this for proprietary software? I knew about the server stuff, but I didn’t think the AGPL bound compiled programs to the terms of the compiler.
If I use an AGPL text editor, does my written text also become APGL?
- e12e 7y agoImpossible to use for proprietary software you distribute. So you can write internal software, and only need to share the source with yourself.
- mumblemumble 7y agoProbably more poignantly, it's not usable for open source projects that want to distribute their stuff under a license that's more permissive than the AGPL. Which I'm guessing is intentional.
- e12e 7y agoWell, it only prevents distributing binaries. You could still do source only distribution.
- deleted 7y ago[deleted]
- _ph_ 7y agoAn (A)GPL text editor works, see for example Emacs, as the text created doesn't contain any part of the editor itself. But a compilers emits code which is based on your source and the compiler itself. Also, it usually links against a standard library which would be AGPL. So this makes your created executable AGPL unless there is an explicit excemption, as it is the case with GCC.