From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-user@gnu.org, guile-devel@gnu.org, guile-sources@gnu.org,
info-gnu@gnu.org
Subject: GNU Guile 2.2.6 released
Date: Sun, 30 Jun 2019 23:57:34 +0200 [thread overview]
Message-ID: <87ef3arb1t.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3836 bytes --]
We are delighted to announce GNU Guile release 2.2.6, the sixth bug-fix
release in the 2.2 stable release series. See the NEWS excerpt that
follows for full details.
* * *
Guile is an implementation of the Scheme programming language.
The Guile web page is located at https://gnu.org/software/guile/, and
among other things, it contains a copy of the Guile manual and pointers
to more resources.
Guile can run interactively, as a script interpreter, and as a Scheme
compiler to VM bytecode. It is also packaged as a library so that
applications can easily incorporate a complete Scheme interpreter/VM.
An application can use Guile as an extension language, a clean and
powerful configuration language, or as multi-purpose "glue" to connect
primitives provided by the application. It is easy to call Scheme code
from C code and vice versa. Applications can add new functions, data
types, control structures, and even syntax to Guile, to create a
domain-specific language tailored to the task at hand.
Guile implements many common Scheme standards, including R5RS, R6RS, and
a number of SRFIs. In addition, Guile includes its own module system,
full access to POSIX system calls, networking support, multiple threads,
dynamic linking, a foreign function call interface, and powerful string
processing.
Guile 2.2.6 can be installed in parallel with Guile 2.0.x; see
https://www.gnu.org/software/guile/manual/html_node/Parallel-Installations.html.
* * *
Changes in 2.2.6 (since 2.2.5)
* Bug fixes
** Fix regression introduced in 2.2.5 that would break HTTP servers
Guile 2.2.5 introduced a bug that would break the built-in HTTP server
provided by the (web server) module. Specifically, HTTP servers would
hang while reading requests. See <https://bugs.gnu.org/36350>.
** 'strftime' and 'strptime' honor the current locale encoding
Until now these procedures would wrongfully assume that the locale
encoding is always UTF-8. See <https://bugs.gnu.org/35920>.
** Re-export 'current-load-port'
This procedure was erroneously removed in the 2.2 series but was still
documented.
** Minor documentation mistakes were fixed
* * *
Here are the compressed sources:
https://ftp.gnu.org/gnu/guile/guile-2.2.6.tar.gz (18MB)
https://ftp.gnu.org/gnu/guile/guile-2.2.6.tar.lz (9MB)
https://ftp.gnu.org/gnu/guile/guile-2.2.6.tar.xz (11MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/guile/guile-2.2.6.tar.gz.sig
https://ftp.gnu.org/gnu/guile/guile-2.2.6.tar.lz.sig
https://ftp.gnu.org/gnu/guile/guile-2.2.6.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA256 checksums:
08c0e7487777740b61cdd97949b69e8a5e2997d8c2fe6c7e175819eb18444506 guile-2.2.6.tar.gz
1a71fd3d37f97423a402b2e38b1be9d80387dafa5c66fc3e5967307d85624aa5 guile-2.2.6.tar.lz
b33576331465a60b003573541bf3b1c205936a16c407bc69f8419a527bf5c988 guile-2.2.6.tar.xz
[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify guile-2.2.6.tar.gz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.16.1
Libtool 2.4.6
Makeinfo 6.5
Gnulib v0.1-1157-gb03f418
Happy hacking with Guile!
Ludovic Courtès, Mark H Weaver, and Andy Wingo.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
reply other threads:[~2019-06-30 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ef3arb1t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=info-gnu@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).