Well, outside of the "flame wars", I think that this it is a genuine problem that has to be solved by Alex.
Using readline for pil21 in the current form requires him to use GPL for Picolisp. I know it's nasty and almost nobody likes that, but it is the way the GPL license works, at least on paper. If anyone will complain in the future about him not doing that has to be seen, but legally he's on the weak side. Let's close this topic by putting the possible options on the table - Alex will have to take a decision: * use readline and make pil21 GPL * Make readline optional (i.e. that can be activated via config), maybe with a thin pil interface calling readline via native. The interface file will be GPL, but pil can be released with MIT license and the reworked led.l * Ditch readline completely and use an alternative with a more permissive license Any other suggestion is welcome. :) Regards, Davide On Sun, Nov 22, 2020, 14:25 Alexander Burger <a...@software-lab.de> wrote: > On Sun, Nov 22, 2020 at 07:36:57AM -0500, r cs wrote: > > Have you been putting up with flame wars this often in the past, or is it > > worse during COVID-19? > > No flame war please! :) > > The question came up at PilCon, so I asked here. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > >
