On Sun, Nov 22, 2020 at 09:22:29AM +0100, Alexander Burger wrote:
> Yes, I want pil21 as a piece be completely "free", in the spirit of MIT.
corporations tend to abuse the idealist "spirit of free" often. I prefer
something in the middle of GPL and MIT which LGPL does in many cases.
The practi
On Sun, Nov 22, 2020 at 09:03:47AM +0100, Tomas Hlavaty wrote:
> On Sun 22 Nov 2020 at 01:32, Alexander Williams wrote:
> > Not a lawyer here, but PicoLisp 21 does **not** need to be GPL'd.
>
> it does not because it is already compatible with GPL
>
> > Everyone seems to confuse "linking to a GP
my vote to go for GPL and readline. As you said compatibility is guaranteed
and everybody knows it.
On Sat, Nov 21, 2020 at 9:23 AM Alexander Burger
wrote:
> Hi all,
>
> at yesterday's PilCon it turned out that pil21 has a serious licence
> problem.
>
> A major design decision of pil21 was to us
I think it should be fine. Picolisp is distributed as source code. The code
implementing readline can be GPL licensed. The code implementing everything
else can be a less restrictive license if desired. Binaries including
readline can be distributed as GPL, binaries without readline can be MIT.
The
Look, the FSF own readline. They want every program that uses readline
to be released under the GPL. This may be antisocial of them, but
unless you specifically want to annoy them, you can either comply with
their conditions or stop using their code.
Sean Case
--
UNSUBSCRIBE: mailto:picolisp
On Sun 22 Nov 2020 at 12:09, Alexander Burger wrote:
> On Sun, Nov 22, 2020 at 11:49:11AM +0100, Tomas Hlavaty wrote:
>> it is only mess because you really want to find a loophole
>
> I don't want to find a loophole. I leave everything as it is (MIT/X11). I just
> want to point out how nonsensical
On Sun 22 Nov 2020 at 11:16, Alexander Williams wrote:
> Tomas, you're allowed to relicense the MIT version of PicoLisp you
> received, as GPLv3, as long as you maintain the MIT license text.
what about customers that ban GPL on their machines?
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?s
Tomas, you're allowed to relicense the MIT version of PicoLisp you
received, as GPLv3, as long as you maintain the MIT license text.
AW
On Sun, 22 Nov 2020, Tomas Hlavaty wrote:
what if i don't want to risk going to court because of this?
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?sub
On Sun, Nov 22, 2020 at 11:49:11AM +0100, Tomas Hlavaty wrote:
> it is only mess because you really want to find a loophole
I don't want to find a loophole. I leave everything as it is (MIT/X11). I just
want to point out how nonsensical it all is.
> otherwise you could use rlwrap as already sugg
On Sun 22 Nov 2020 at 11:12, Davide BERTOLOTTO
wrote:
> Right, but apparently nobody went to court for such topics, so it is still
> gray zone.
what if i don't want to risk going to court because of this?
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
On Sun 22 Nov 2020 at 11:23, Alexander Burger wrote:
> On Sun, Nov 22, 2020 at 11:03:31AM +0100, Alexander Burger wrote:
>> In my understanding it is irrelevant how the library is linked, or the fact
>> that
>> pil21 "depends" on it
>
> This is all such a mess! What is "linking" other than callin
>From the wiki page they you shared, quoting the FSF
Where's the line between two separate programs, and one program with two
parts? This is a legal question, which ultimately judges will decide. We
believe that a proper criterion depends both on the mechanism of
communication (exec, pipes, rpc, f
Hi Davide,
> Anyway, Alex what about this editline (not to be confused with the BSD
> one)? It may be enough for pil21 implementation:
> https://github.com/troglobit/editline#introduction
I believe it cannot do what I need.
I decided to abandon the @lib/led.l used in pil32 / pil64 and instead us
On Sun, Nov 22, 2020 at 11:03:31AM +0100, Alexander Burger wrote:
> In my understanding it is irrelevant how the library is linked, or the fact
> that
> pil21 "depends" on it
This is all such a mess! What is "linking" other than calling external code at
runtime?
In pil you can call any other lib
On Sun, Nov 22, 2020 at 11:03:31AM +0100, Alexander Burger wrote:
> In my understanding it is irrelevant how the library is linked, or the fact
> that
> pil21 "depends" on it, as long as it is not distributing (modified (derived)
> or
> not) parts of libreadline.
According to https://en.wikipedi
Right, but apparently nobody went to court for such topics, so it is still
gray zone.
Anyway, Alex what about this editline (not to be confused with the BSD
one)? It may be enough for pil21 implementation:
https://github.com/troglobit/editline#introduction
On Sun, Nov 22, 2020, 10:22 Tomas Hlava
Hi Davide, Tomas,
On Sun, Nov 22, 2020 at 10:07:44AM +0100, Tomas Hlavaty wrote:
> Hi Alex,
>
> On Sun 22 Nov 2020 at 09:22, Alexander Burger wrote:
> > Yes, I want pil21 as a piece be completely "free", in the spirit of MIT.
>
> then it cannot depend on GPL library
I do not think so.
The
On Sun 22 Nov 2020 at 09:59, Davide BERTOLOTTO
wrote:
> In my personal opinion it will be okay if we use the readline library in
> pil21, since it is a *library* and we are not making a 'derivative' work
> out of it
this is wrong
there is exactly the same precedent already, see clisp
https://ra
Hi Alex,
On Sun 22 Nov 2020 at 09:22, Alexander Burger wrote:
> Yes, I want pil21 as a piece be completely "free", in the spirit of MIT.
then it cannot depend on GPL library
>>From what I underseod so far, the GPL is all about "distributing". PicoLisp
>>does
> *not* distribute any GPLed code (
According to the GPL FAQ *technically* a dynamically linked object still
falls under GPL
https://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDynamic
However it seems that not everyone agrees on that fundamentalist view:
https://www.linuxjournal.com/article/6366
As far as I know, there has not
Hi Tomas,
> even though pil21 is MIT licensed, the GPL dependency makes the combined
> work GPL licensed
>
> if i understand the raised issue correctly, alex wants the combined work
> to be MIT licensed, which means pil21 cannot depend on GPL software
On Sun, Nov 22, 2020 at 09:08:32AM +0100, To
On Sun 22 Nov 2020 at 07:00, Alexander Burger wrote:
> It is not even linked at *compile* time, but - dynamically - at runtime
> (shared library).
i don't think this makes any difference
the question is: does pil21 depend on GPL software? if yes, the
combined work has GPL licence. if not, pil2
On Sun 22 Nov 2020 at 01:32, Alexander Williams wrote:
> Not a lawyer here, but PicoLisp 21 does **not** need to be GPL'd.
it does not because it is already compatible with GPL
> Everyone seems to confuse "linking to a GPL'd library that exists on the
> host computer" VS "linking to a GPL'd lib
Thanks Alexander,
thanks for this plausible explanations!
> Not a lawyer here, but PicoLisp 21 does **not** need to be GPL'd.
>
> Everyone seems to confuse "linking to a GPL'd
> library that exists on the host computer" VS
> "linking to a GPL'd library that's included
> with the source code".
I don't see what all the confusion is about.
Not a lawyer here, but PicoLisp 21 does **not** need to be GPL'd.
Everyone seems to confuse "linking to a GPL'd library that exists on the
host computer" VS "linking to a GPL'd library that's included with the
source code".
Please stop mixing thes
I built mruby from AUR and when I do ldd there is no linking to libreadline:
linux-vdso.so.1 (0x7ffe02708000)
> libm.so.6 => /usr/lib/libm.so.6 (0x7f6f005cb000)
> libc.so.6 => /usr/lib/libc.so.6 (0x7f6f00402000)
> /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2
> (0x
> On Nov 21, 2020, at 15:30, Jeronimo Pellegrini wrote:
>
> "Mike" writes:
>
> Hello,
>
>> Jeronimo,
>> mruby is not ruby itself, but also created by Matsumoto.
>> https://github.com/mruby/mruby
>> I see this is under MIT.
>>
>> How it was possible ?
>
> But is it distributed with/links t
Hi,
> The software modules that link with the library may be under various GPL
> compatible licenses, but the work as a whole must be licensed under the
> GPL
Also found this
https://opensource.stackexchange.com/questions/6062/using-gpl-library-with-mit-licensed-code
Damn, this is
Jeronimo,
mruby is not ruby itself, but also created by Matsumoto.
https://github.com/mruby/mruby
I see this is under MIT.
How it was possible ?
November 21, 2020 2:15 PM, "Jeronimo Pellegrini" wrote:
> "Mike" writes:
>
>> hi all,
>>
>>> at yesterday's PilCon it turned out that pil21 has
hi all,
> at yesterday's PilCon it turned out that pil21 has a serious licence problem.
>
We already discussed this pseudo problem with Alex in Delta Chat thread.
If I understand now correctly this is not a problem and Pil21 should keep using
readline GPL library and be covered by MIT/X11 lic
libedit probably not a suitable replacement:
https://github.com/conda-forge/python-feedstock/issues/387
> OK, let me rephrase, then. I am that person. I work on some other projects
> that use readline/libedit. I can tell you that it is a huge headache, even
> on Mac, when libedit is used instead.
Thanks Mike!
this looks good indeed!
☺/ A!ex
On Sat, Nov 21, 2020 at 09:45:42AM +, Mike wrote:
> 1.
> Lets take a real world example, get all packages of ArchLinux required by
> readline, "Required By (133)" on the right:
> https://www.archlinux.org/packages/core/x86_64/readline/
>
>
> ht
On Sat, Nov 21, 2020 at 10:41:23AM +0200, Yiorgos [George] Adamopoulos wrote:
> Do you absolutely need this? Why not remove it all and work with rlwrap
> when you need command line editing?
No way. Check pil21/src/lib.c
pil21 needs a lot of stuff to interoperate with the command line.
And, as I
Do you absolutely need this? Why not remove it all and work with rlwrap
when you need command line editing?
On Sat, 21 Nov 2020 at 10:23 AM Alexander Burger
wrote:
> Hi all,
>
> at yesterday's PilCon it turned out that pil21 has a serious licence
> problem.
>
> A major design decision of pil21 w
Hi all,
at yesterday's PilCon it turned out that pil21 has a serious licence problem.
A major design decision of pil21 was to use readline(3) instead of the self-
rolled @lib/led.l from pil64/pil32.
The reason was compatibility with the rest of the world (readline supports both
vi- and emacs-mod
35 matches
Mail list logo
