Re:FSF Wastes Away Another "High Priority" Project
by tomjen3 on Thursday January 24, 2013 @02:22PM
(#5111545)
What I never really understood was why nobody ever cloned readline? Clisp was open sourced because they used readline, but they already had a completely working common lisp system with everything -- how hard can it be to write a readline library?
Re:FSF Wastes Away Another "High Priority" Project
by fluidcruft on Thursday January 24, 2013 @02:28PM
(#5111588)
NetBSD created a readline compatible library called editline.
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libedit/?sortby=...
The BSD crowd has been slowly chipping away at replacing all the GNU stuff they expediently adopted following the AT&T lawsuit.
Broadly speaking the rule of thumb is that if something makes use of internal knowledge of GPL code implementation or function (i.e. unique data structures/objects/functions that are not considered "standard"), it's considered a derivative work (this is also how the Linux kernel approaches GPL vs non-GPL drivers, too). If all it were to take was to adapt and repackage a GPL project as a dynamically loaded library, the GPL would be meaningless.
In my mind, the really hairy area is where certain projects seem to be allowed to define "public" APIs that surrender GPL protection and allow use of closed binary libraries (i.e. the Linux kernel's public driver interface or Octave's MEX interface). Or what happens when the BSD folks just copy your API and re-implement everything (undermining the uniqueness of the GPL software's internals)? Don't bring this up to the FSF though, they suddenly switch from being eloquent to pretending to be dense.