now, far as I'm concerned, the parsers are just outputs of the program, and not the program itself, and so are not covered
-
Show this thread
-
however, the gcc runtime library exception is a thing
1 reply 0 retweets 0 likesShow this thread -
and given the output of this program is itself another program...
1 reply 0 retweets 0 likesShow this thread -
I don't have the legal chops to get into defining these things accurately or drawing up terms and I'm not hiring a lawyer either
1 reply 0 retweets 0 likesShow this thread -
(I kind of see the program vs data question is an unfathomable philosophical question, and the law is super weird, but)
1 reply 0 retweets 2 likesShow this thread -
other solution: give them a commercial license, except I'm not getting set up for VAT &c just to service this one-off thing
1 reply 0 retweets 1 likeShow this thread -
plus I don't support this thing enough to reasonably offer it commercially, unless demand suddenly jumps
1 reply 0 retweets 0 likesShow this thread -
so: does anyone know a good off-the-shelf thing you can use to cover outputs from GPL-licensed compilers/build tools?
1 reply 0 retweets 0 likesShow this thread -
b/c given the above and the precedent set by gcc I'm probably going to have to say the output is also GPL unless I can exempt it nicely
3 replies 0 retweets 0 likesShow this thread -
but also: I have deliberately picked GPL to discourage usage by people that dislike it
2 replies 0 retweets 2 likesShow this thread
You reap what you sow man. If you want to discourage use by ppl who dislike GPL, tell them no.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.