From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Guile User List <guile-user@gnu.org>
Subject: Re: mod_lisp support for guile-www
Date: Sat, 13 Mar 2010 05:16:14 +0100 [thread overview]
Message-ID: <87zl2crh4h.fsf@ambire.localdomain> (raw)
In-Reply-To: <877hphl1ws.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 12 Mar 2010 20:29:07 +0000")
() Neil Jerram <neil@ossau.uklinux.net>
() Fri, 12 Mar 2010 20:29:07 +0000
Would it really be stepping on their toes? AFAICT they only use Guile
for configuration, whereas Guile-WWW's purpose is to provide function to
Guile applications.
Serveez is a general protocol handling (big dishing loop around select(2))
framework, that you can use instead of Guile-WWW. However, it is not being
maintained last time i checked, so any toes-stepping is just theoretical...
I think my personal preference would be not to maintain it as an
individual package, but to roll it into the Guile distribution. Would
you be happy with that?
Not really (this ties in with the license)...
I note that Guile-WWW's license is GPLv3+, whereas the Guile
distribution as a whole is LGPLv3+. I'm not sure if that's a problem or
not; I think I remember hearing that there are already other pieces of
code that came from guile-library and that have different licenses.
I think it is better not to combine these for licensing reasons. I
consciously chose GPLv3+ and would be disappointed to see Guile-WWW
revert to any lesser license.
Apart from the licensing, there is a good technical reason: separation allows
Guile-WWW to be used by other Guile versions. (I'm still playing w/ Guile
1.4, for example.)
thi
next prev parent reply other threads:[~2010-03-13 4:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 23:00 mod_lisp support for guile-www Neil Jerram
2010-03-09 16:30 ` Thien-Thi Nguyen
2010-03-12 20:29 ` Neil Jerram
2010-03-12 21:45 ` Ludovic Courtès
2010-03-12 23:21 ` Neil Jerram
2010-03-13 4:16 ` Thien-Thi Nguyen [this message]
2010-03-16 19:48 ` Neil Jerram
2010-03-16 22:48 ` Ludovic Courtès
2010-06-17 21:42 ` Thien-Thi Nguyen
2010-07-06 23:04 ` Neil Jerram
2010-07-06 23:48 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zl2crh4h.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).