From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Re: ttn-pers-scheme & ttn-do
Date: Sat, 12 Apr 2008 19:36:24 +0300 [thread overview]
Message-ID: <87wsn33u9j.fsf@moley.moleskin.org> (raw)
In-Reply-To: 878wzvkwiq.fsf@ambire.localdomain
Quoth Thien-Thi Nguyen <ttn@gnuvola.org>:
> () Sebastian Tennant <sebyte@smolny.plus.com>
> () Wed, 19 Mar 2008 13:08:37 +0200
>
> What was this special exception and was it the reason for the fork?
>
> The fork was over deprecation of some libguile API elements, plus
> administrative snafu. The special exception can be seen in some Guile
> releases in the top-level README:
>
> | The exception is that, if you link the GUILE library with other files
> | to produce an executable, this does not by itself cause the
> | resulting executable to be covered by the GNU General Public License.
> | Your use of that executable is in no way restricted on account of
> | linking the GUILE library code into it.
Very interesting. Presumably this is/was to encourage use of Guile
across the board (i.e., in non-free environments too)?
> Good luck. I'd be very interested to know a little more about the
> politics e.t.c.... perhaps off-list?.. even though you describe the fork
> as amicable.
>
> Here's my recollection of events:
Thanks for taking the time to write this. I can't say exactly _why_
it's nice to know how the situation came about, but it is, nevertheless.
> So i see 1.4.x not really so much a fork as a long-lived non-local
> branch. Now that there is new Guile maintainership, i think it would be
> a good idea to merge some of the good stuff from that branch into the
> trunk.
I'd say so. As someone who wants to use Guile for scripting
database-backed websites and the like, guile-pg and guile-www are two
essential components. Fortunately your guile-www _does_ work with
guile-1.8.
> Git supports branches much better than cvs, so there is now even
> less reason for the shutout.
I hope the maintainers are listening. Surely it's time to let bygones
be bygones and work for the common good of Guile and all who sail in
her.
> We all cope as best we can.
Indeed we do. Thanks for your comprehensive and informative reply.
Sebastian
--
Emacs' AlsaPlayer - Music Without Jolts
http://sebyte.org/eap.html
next prev parent reply other threads:[~2008-04-12 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 20:20 ttn-pers-scheme & ttn-do Sebastian Tennant
2008-03-19 7:35 ` Thien-Thi Nguyen
2008-03-19 11:08 ` Sebastian Tennant
2008-04-03 11:28 ` Thien-Thi Nguyen
2008-04-03 11:47 ` Thien-Thi Nguyen
2008-04-12 16:36 ` Sebastian Tennant [this message]
2008-05-25 18:12 ` 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=87wsn33u9j.fsf@moley.moleskin.org \
--to=sebyte@smolny.plus.com \
--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).