Closed shakatoday closed 1 year ago
All looks good to me merging.
Since CLAK is the only "lgpl" portion of clog and that creates some issues for some companies, we will likely have to support a hunchentoot direct version in the future. I have had two requests already. One already sent two emails with no response so far to Fukamachi to see if would consider switching license. Don't know if you have a better way to reach, would be good to leave as is.
Proprietary softwares can include LGPL libraries. There should be no problems. Could you explain the issues a bit? https://twitter.com/nitro_idiot As far as I know, Fukamachi is probably active on Twitter. I only met him in two Common Lisp activities in Japan, so I guess I can't do the referral well.
I'll send this URL about our communication to another Lisper I'm more familiar with, who is much closer to Fukamachi.
I do think it would be nice if woo worked too :)
On Tue, Aug 9, 2022 at 9:17 PM David Botton @.***> wrote:
I personally don't care if lgpl (I have written volumes of it in Ada) or not, but apparently some lawyers in the US question have a big X on it perhaps related to using it in a lisp image.
I can't imagine though there is much to gain virus licensing clack anyways, I wonder why do it to start with when tons of his code are MIT/BSD.
Thanks!
On Tue, Aug 9, 2022 at 9:11 PM Shaka Chen @.***> wrote:
Proprietary softwares can include LGPL libraries. Could you explain the issues a bit? https://twitter.com/nitro_idiot As far as I know, Fukamachi is probably active on Twitter. I only met him in two Common Lisp activities in Japan, so I guess I can't do the referral well.
I'll send this URL about our communication to another Lisper I'm more familiar with, who is much closer to Fukamachi.
— Reply to this email directly, view it on GitHub https://github.com/rabbibotton/clog/pull/205#issuecomment-1210041173, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYUEFPYKJG2ZCPBLLUQM6TVYL6S3ANCNFSM557XRP2A . You are receiving this because you modified the open/close state.Message ID: @.***>
Thank you for explanation. The licenses of those libraries are LLGPL provided by U.S. based Franz Inc. As U.S. being a Common Law country, I guess the problem could be that for Lisp libraries with LLGPL (or LGPL) there have been not enough precedents on the court.
This legal issue is too big to me. I've sent the URL of this thread to the Lisper I mentioned, who is close to Fukamachi.
I think Fukamachi will reply tweets & messages on his Twitter, though. https://twitter.com/nitro_idiot
Hi, I'm the author of Clack/Lack.
I don't think the LLGPL license will be any legal problems while Clack and Lack are used just as a library, as Shaka said. However, I learned that some people tend to dislike GPL-like licenses emotionally, not legally.
So, I changed those licenses to MIT. We are in a small community, so let's help where we can.
I agree :)
Truly appreciated! Thanks!
I personally don't care if lgpl (I have written volumes of it in Ada) or not, but apparently some lawyers in the US question have a big X on it perhaps related to using it in a lisp image.
I can't imagine though there is much to gain virus licensing clack anyways, I wonder why do it to start with when tons of his code are MIT/BSD.
Thanks!
On Tue, Aug 9, 2022 at 9:11 PM Shaka Chen @.***> wrote:
Proprietary softwares can include LGPL libraries. Could you explain the issues a bit? https://twitter.com/nitro_idiot As far as I know, Fukamachi is probably active on Twitter. I only met him in two Common Lisp activities in Japan, so I guess I can't do the referral well.
I'll send this URL about our communication to another Lisper I'm more familiar with, who is much closer to Fukamachi.
— Reply to this email directly, view it on GitHub https://github.com/rabbibotton/clog/pull/205#issuecomment-1210041173, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYUEFPYKJG2ZCPBLLUQM6TVYL6S3ANCNFSM557XRP2A . You are receiving this because you modified the open/close state.Message ID: @.***>
Brief
More Info
API for Prepending Lack Middleware
I want it. Please let me add this if you think that's ok. 😁
Coding style tweak
Fixed an emergent bug after adding the Lack Middleware api.
Environments
Operating System & Hardware: MacOS Monterey 12.5 with M1 Pro Common Lisp Implementation: SBCL 2.2.5 Browser: Safari Version 15.6 (17613.3.9.1.5)
Reproduction
The bug had appeared whenever adding more than 1 Lack Middlewares by :lack-middleware-list. If anyone is interested, you here's the branch to reproduce the bug. error-test-case-when-x-www-form-urlencoded-and-more-middlewares
To load "lack-middleware-session": Load 1 ASDF system: lack-middleware-session ; Loading "lack-middleware-session"
Fix
This commit fixed the error. fixed read-sequence type error when there are more lack middlewares
I didn't add
circular-streams
intoclog.asd
becauselack-request
has already depended oncircular-streams
,On this branch error-fixed-with-test-case-for-api-for-lack-middleware you can test the patch since it also contains a modified version of tutorial 17 with 2 prepended lack middlewares.