5 ms·
Hey Koen! From the perspective of a person who chooses the GPL license for their code, the issue is that they want to the right to take your changes and then m
by boucher 17y ago
Hey Koen!
From the perspective of a person who chooses the GPL license for their code, the issue is that they want to the right to take your changes and then modify them as they see fit.
The GPL prefers that right over everything else, including overall use of any particular program or library. GPL advocates would suggest that it is in fact bad that you've increased the use of subversion, because you've done it in a way that all those new users can't go in and fix bugs in your program, or change some behavior that they feel needs changing.
I think one of the reasons people fail to understand this argument is that they see a complete disconnect between end users and developers. In other words, an end user is someone who will never even want to edit source code. I'm inclined to think this is usually true, but the authors of the GPL are the exception to that rule, and it is one of the primary reasons that the GPL exists.
As far as the git client is concerned, wrapping the command line, as you suggested, basically solves the problem. It's also probably not that hard. In fact, there are a couple ruby libraries that do it I believe, and maybe python ones as well, if you're still doing PyObjc.
- tlrobinson 17y agoLGPL would be a good choice for something like Git, so you can still use it in proprietary software, but any improvements to Git itself must be contributed back.