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 3.0.4 released
Date: Wed, 24 Jun 2020 16:48:43 +0200 [thread overview]
Message-ID: <875zbgwmd0.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3478 bytes --]
We are pleased but also embarrassed to announce GNU Guile release 3.0.4.
This release fixes the SONAME of libguile-3.0.so, which was wrongfully
bumped in 3.0.3. Distributions should use 3.0.4. Apologies!
* * *
The Guile web page is located at http://gnu.org/software/guile/, and
among other things, it contains a copy of the Guile manual and pointers
to more resources.
Guile is an implementation of the Scheme programming language, packaged
for use in a wide variety of environments. In addition to implementing
the R5RS, R6RS, and R7RS Scheme standards, Guile includes full access to
POSIX system calls, networking support, multiple threads, dynamic
linking, a foreign function call interface, powerful string processing,
and HTTP client and server implementations.
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 3.0 can be installed in parallel with Guile 2.2.x; see
http://www.gnu.org/software/guile/manual/html_node/Parallel-Installations.html.
* * *
Changes in 3.0.4 (since 3.0.3)
This release fixes the SONAME of libguile-3.0.so, which was erroneously
bumped in 3.0.3 compared to 3.0.2. Distributions are strongly
encouraged to use 3.0.4 instead of 3.0.3.
Thanks to Chris Vine for reporting the issue.
* * *
Here are the compressed sources:
https://ftp.gnu.org/gnu/guile/guile-3.0.4.tar.gz (21MB)
https://ftp.gnu.org/gnu/guile/guile-3.0.4.tar.lz (11MB)
https://ftp.gnu.org/gnu/guile/guile-3.0.4.tar.xz (13MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/guile/guile-3.0.4.tar.gz.sig
https://ftp.gnu.org/gnu/guile/guile-3.0.4.tar.lz.sig
https://ftp.gnu.org/gnu/guile/guile-3.0.4.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA256 checksums:
13f2f61a665469d330e651c8e9f7faecbb87fe474767f9532f2e821701730957 guile-3.0.4.tar.gz
f2b0b66fd72bc24df76856e1549bf327c025b8a5d5fa3cb1696327c5941c89c4 guile-3.0.4.tar.lz
6b7947dc2e3d115983846a268b8f5753c12fd5547e42fbf2b97d75a3b79f0d31 guile-3.0.4.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-3.0.4.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 pool.sks-keyservers.net \
--recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.16.2
Libtool 2.4.6
Makeinfo 6.7
Gnulib v0.1-1157-gb03f418
Happy hacking with Guile!
Ludovic Courtès and Andy Wingo.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
reply other threads:[~2020-06-24 14:48 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=875zbgwmd0.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).