3 ms·
I think it is mainly due to their concerns over the Tivoization clause which is added to GPLv3
by wongmjane 9y ago
I think it is mainly due to their concerns over the Tivoization clause which is added to GPLv3
- chocolatebunny 9y agoThat's true for any developer of embedded software. Any one who makes hardware of any kind will avoid trying to put any GPLv3 licensed code on their hardware.
- DannyBee 9y agoAgain, no, we didn't care. First: We were already publishing all our GCC changes, as we did all our work upstream (we worked on a staging branch in the gcc repo, and changes were moved to trunk as fast as possible) Plenty of other companies used our branch and we were happy with it. We do all our work upstream for clang/llvm as well, and pull compiler releases when upstream is green according to our internal testing. (Pretty much the only cherry picks are a small number of reverts sometimes) Second, literally nobody has ever come and expressed a concern about using GCC to me. I've had to explain the runtime and libstdc++ exceptions to people, but that was the other way around -- They weren't worrying, and I needed to make sure they worried and shipped source when they ship it as a .so.