From: David Pirotte <david@altosw.be>
To: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Guile-Lib 0.2.6.1 released
Date: Mon, 9 Jul 2018 10:32:58 -0300 [thread overview]
Message-ID: <20180709103258.26f849ad@capac> (raw)
[-- Attachment #1: Type: text/plain, Size: 2428 bytes --]
Hello,
We are pleased to announce Guile-Lib 0.2.6.1. This is a maintenance release,
see below for a list of visible changes since 0.2.6.
* Guile-Lib Homepage:
http://www.nongnu.org/guile-lib/
* Guile-Lib release tarball GPG signature [*]:
http://download.savannah.gnu.org/releases/guile-lib/guile-lib-0.2.6.1.tar.gz
http://download.savannah.gnu.org/releases/guile-lib/guile-lib-0.2.6.1.tar.gz.sig
[ Downloads will redirect to your nearest mirror site.
[ Files on mirrors may be subject to a replication delay of up to 24 hours.
[ In case of problems use
[ http://download-mirror.savannah.gnu.org/releases/guile-lib/
* About Guile-Lib
Guile-Lib is intended as an accumulation place for pure-scheme Guile modules,
allowing for people to cooperate integrating their generic Guile modules into a
coherent library. Think "a down-scaled, limited-scope CPAN for Guile".
* Changes since 0.2.6
Here is a summary of the changes since version 0.2.6. See Guile-Lib's
[[http://git.savannah.nongnu.org/cgit/guile-lib.git][git summary]] and
[[http://git.savannah.nongnu.org/cgit/guile-lib.git/log/][git log]] for a complete
description.
** Configure msgs improved
The configure step NOTICE and WARN msgs (the latter being displayed when
--with-guile-site="no") have been slightly improved.
** Guile-Lib's pkg-config file
Receives one more variable: guile_site=[yes|no].
** Bugs fixed
The script pre-inst-env.in has been fixed so it properly sets
GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH (thanks to Ludovic Courtès
who reported this bug).
* This release was bootstrapped using the following tools:
-] autoconf (GNU Autoconf) 2.69
-] automake (GNU automake) 1.15.1
-] makeinfo (GNU texinfo) 6.5
-] pdflatex 3.14159265-2.6-1.40.19 (TeX Live 2018/Debian)
-] guile-2.2 2.2.4.1-cdb19
On behalf of the Guile-lib team,
David
[*] 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-lib-0.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 A3057AD7
and rerun the 'gpg --verify' command.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-07-09 13:32 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=20180709103258.26f849ad@capac \
--to=david@altosw.be \
--cc=guile-devel@gnu.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).