News for hackers. Stuff that matters.
Re:Things to Know About GNU Readline by kazinator on Thursday August 22, 2019 @08:48PM (#20773718)
I believe they could easily have wriggled out of it.

You can't infringe on the GNU license of something that is 1) not shipped with your program and 2) your program runs fine without.

CLISP has a very good FFI which could be used to attach to a user's readline installation dynamically, if so configured by the end user.

This be packaged up in .lisp file that is not even officially bundled with CLISP. Thus if there was any shred of a basis for infringment, the only offender would be that file, which anyone could share over obvious channels. (Good luck suing a file circulating on the Internet, or having all copies of it taken down ...)

If I have a proprietary or otherwise GNU-incompatible program, and some GNU library, and as user (not redistributing anything!) want to put that together with the help of some config file on the Internet, what is the basis for stopping me? And would RMS even support a state with the level of surveillance required to catch people in such acts ...

Re:Things to Know About GNU Readline by admax88q on Thursday August 22, 2019 @09:43PM (#20773948)
Or just don't be a prick and write your own readline if the terms of the GNU version are not to your liking.

HN is a strange place where people will bemoan piracy but salivate at ways to workaround the GPL.

Re:Things to Know About GNU Readline by cat199 on Thursday August 22, 2019 @11:26PM (#20774302)
or, do!

https://github.com/NetBSD/src/tree/trunk/lib/libedit

also:

isn't the entire GNU project itself someone 'being a prick and writing their own unix because the terms of the AT&T one were not to their liking'?

(pay no attention to the Berkely UNIX behind the curtain)

also also:

isn't this hacker news?

Re:Things to Know About GNU Readline by gwd on Friday August 23, 2019 @05:50AM (#20775881)
Nitpick: "Being a prick" in the parent was "trying to work around the license". "Writing your own alternative" was the "don't be a prick" option.

Of course, just because you write your own alternative doesn't mean you can't be a prick if you want. :-)

Re:Things to Know About GNU Readline by cat199 on Saturday August 24, 2019 @06:32PM (#20790133)
think the above was ambiguous language. could go either way.

but yes, could be a misreading. cheers.

Re:Things to Know About GNU Readline by aidenn0 on Friday August 23, 2019 @11:50AM (#20778829)
It's more of a gray area because the same author wrote them and clearly intended them to be used together. Intent can be a very large factor in civil cases.
Re:Things to Know About GNU Readline by kazinator on Friday August 23, 2019 @03:28PM (#20781613)
If the file which loads readline andmakes it available for use is GPL-ed, I don't see any legal, let alone moral problem.

I can write a readline.lisp file for, say, LispWorks (proprietary, closed-source Lisp) which loads GNU readline and binds to it. Just my file has to be GPL-ed (no distributing it in compiled format only, etc). It doesn't make LispWorks violate the GPL.

I can cheerfully combine that GPL-ed file with readline, and make a distribution that I can give to users of the proprietary Lisp.

Those users are receiving my readline.lisp and readline in accordance with the GPL, and can use these however they want.

If I can do that, someone at LispWorks could do that too.