Yeah, that adds a fairly terrible level of inflexibility for sure if you're working on a proprietary product. On a non-commercial level, it causes friction with anything licensed as BSD/MIT/Apache/etc, and that puts a lot of projects out in the cold.
I can't imagine too many cases where readline would get pulled into my proprietary code as a transitive dependency. I mentioned psql above: it's not as though I'd have `#include "psql.h"` in my own project.
What's this friction between readline and other licenses in other Free Software code? Unless I'm writing some software with a non-GPL license and want to include GPLed software in my own that I plan to distribute, it doesn't affect me.
Comments
Yeah, that adds a fairly terrible level of inflexibility for sure if you're working on a proprietary product. On a non-commercial level, it causes friction with anything licensed as BSD/MIT/Apache/etc, and that puts a lot of projects out in the cold.
I can't imagine too many cases where readline would get pulled into my proprietary code as a transitive dependency. I mentioned psql above: it's not as though I'd have `#include "psql.h"` in my own project.
What's this friction between readline and other licenses in other Free Software code? Unless I'm writing some software with a non-GPL license and want to include GPLed software in my own that I plan to distribute, it doesn't affect me.
Python?
Python optionally uses libedit.
Was going to mention that. libedit seems to provide a sufficient subset of command line editing functionality for most purposes.