Re: [TCLCORE] GPL Licence in TCLLib added

[Kevin W. <kw...@co...>]

<div><img width="1" height="1" src='https://fedbdhd.r.af.d.sendibt2.com/tr/op/TIJzNa2Aa0tln5NC8hptS0VD99fDxW6cnxez2TAYpYT_BNrf7evUp9nCtNnfLhVWbEczxFc7nlI9cXxFwBjonfKJ3nrqsPaE0RPTbAdzYg9xXMHrVvsgoR6fOKpqQSN2xiYLmGh7hRIqo5RokV8uL70WuGM8lTptN7G6OygLmErO0hwp-S-df0JS5ZjxfS3w77CG9KkeLJx_VCb46c245yqhv38fw-PT' /></div>On 11/6/24 6:08 AM, Poor Yorick wrote:<br/><br/>> "Contagious" is a mischaracterization.  A project chooses derive its <br/>> work from<br/>> a GPL-licensed work or not.  It doesn't involuntarily "get infected".<br/>> filtergen.tcl is licensed under the GPL, and if it disappears from <br/>> Tcllib,<br/>> where will it be placed?  Some other GPL analogue of Tcllib?  The <br/>> point of<br/>> Tcllib is to make it easier for projects to get their hands on <br/>> software they<br/>> want to use.  Why not then just have branch in Tcllib for such <br/>> things?  Or even<br/>> better just make the license clear and let projects choose for <br/>> themselves what<br/>> works from Tcllib they will use? <br/><br/>The obvious answer to this question is that filtergen.tcl will be <br/>updated with a clean implementation not derived from GPL code, or it <br/>will be removed altogether. That's exactly the choice that the GPL <br/>requires.<br/><br/>The point of tcllib is indeed "to make it easier to projects to get <br/>their hands on projects they want to use." But tcllib has already has a <br/>license, the BSD-style Tcl licnese, and the GPL is not compatible with <br/>this license from the standpoint of developer freedom. That is, if a <br/>developer wants to make code proprietary/closed-source, then any <br/>copyleft-licensed code must be avoided.<br/><br/>--Kevin<br/><br/>