unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: guile-user@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Guile-Lib 0.2.4 released
Date: Mon, 14 Nov 2016 05:53:59 -0200	[thread overview]
Message-ID: <20161114055359.269a5acc@capac> (raw)

[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]

Hello,

We are pleased to announce Guile-Lib 0.2.4. This is a maintenance release, the next
maintenance release for the 0.2 series.


* 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.4.tar.gz
	http://download.savannah.gnu.org/releases/guile-lib/guile-lib-0.2.4.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.3

-  (unit-test)

	The assert-numeric-=  test failed exception report message was
	inadequate and has been fixed.
	
-  Do not check what is not installed

	Starting with Guile-2.0, some Guile-Lib modules became Guile
	core modules, and not installed.  However, we all forgot to
	adapt the test-suite so it does not run any check for none installed
	modules, now fixed.

-  Install source files first

    	Make sure source files are installed first, so that the mtime of
        installed compiled files is greater than that of installed
        source files, in order to avoid a rather annoying local
        (per-user) recompilation of Guile-Lib modules.


* This release was built and tested using the following tools:

 	-] autoconf         		(GNU Autoconf) 2.69 
	-] automake         		(GNU automake) 1.15 
	-] guile-2.0        		2.0.13.1-27247


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.3.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: 455 bytes --]

             reply	other threads:[~2016-11-14  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  7:53 David Pirotte [this message]
2016-11-14  8:01 ` Guile-Lib 0.2.4 released David Pirotte
2017-01-19 13:53 ` Guile-Lib 0.2.5 released Matt Wette

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=20161114055359.269a5acc@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).