[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: License of Hurd's common lisp bindings

From: Maxime Devos
Subject: Re: License of Hurd's common lisp bindings
Date: Thu, 29 Apr 2021 19:06:38 +0200
User-agent: Evolution 3.34.2

Ricardo Wurmus schreef op do 29-04-2021 om 17:29 [+0200]:
> Hi Maxime,
> are you still interested in working on Guile bindings for the 
> Hurd?

I'm still interested, but the conversion Common Lisp -> Scheme
was a lot more tedious and tricky than expected at first, so I
stopped actively working on it. The last commit was three weeks

>   If so, do you have a public repository where we could 
> collaborate?

<https://notabug.org/mdevos/guile-hurd> (branch: scheme-guile)

The current plan is to, in no particular order:

(1) gradually implement more of Common Lisp in "hurd-cl-compat.scm",
    such that more code ‘just compiles’ without source code tweaks
(2) when necessary or more convenient, convert the code to Scheme.
    For example, Scheme conditions do not support multiple inheritance,
    and :before and :after is not supported in GOOPS.
(3) Adjust the public API in mach/, hurd/, ... to Scheme conventions.
    For example: foo-p -> foo?, foo-set --> foo-set!.
(4) Add docstrings

If you create an account at notabug.org, I could grant you commit
access, or we could just use the pull request system.  Commits should
be signed. If you create an account, can you send me a PGP-signed
message with your user name to confirm you're not some imposter?

(Your current key is BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC,

> I second the request for license clarification.  With the GPL, 
> strict versioning without the upgrade clause makes combining works 
> difficult.  One example is the use of Linux code in the Hurd.  If 
> an updated GPLv4 came along, all that GPLv3 only code could not be 
> easily combined with GPLv4 code, which is a complication that is 
> best avoided in the free software realm.

Agreed.  Our intention should probably be documented somewhere and
more formally, in case someone of us meets an untimely demise, preventing
the licensing switch.


Attachment: Maxime Devos.pgp
Description: application/pgp-encrypted

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]