From: David Pirotte <david@altosw.be>
To: guile-user@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Guile-Lib 0.2.3 released
Date: Sun, 18 Sep 2016 23:03:08 -0300 [thread overview]
Message-ID: <20160918230308.46a38a36@capac> (raw)
[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]
Hello,
We are pleased to announce Guile-Lib 0.2.3. This is a maintenance release.
* 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.3.tar.gz
http://download.savannah.gnu.org/releases/guile-lib/guile-lib-0.2.3.tar.gz.sig
* 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.2
This is a maintenance release, source code is unchanged compare to the previous
release. This release introduces a guile-lib-1.0.pc, so libs and apps that needs
guile-lib may now use pkgconfig to check if it's available, what version.
Note that starting with this release, the installation location for modules and
compiled files has changed: make sure you uninstall any previous version.
- Dependencies bumped:
Autogen >= 2.69
Automake >= 1.14
Guile >= 2.0.12
- Modules installation location changed:
from $(prefix)/share/guile/site
to $(GUILE_GLOBAL_SITE)
You will need write privileges to this directory to install guile-lib. You may
check its location using the folowing command:
guile -c "(display (%global-site-dir)) (newline)"
- Compiled files installation location changed:
from $(prefix)/share/guile/site
to $(GUILE_SITE_CCACHE)
You will need write privileges to this directory to install guile-lib. You may
check its location using the folowing command:
guile -c "(display (%site-ccache-dir)) (newline)"
* This release was built/tested using the following tools:
-] autoconf (GNU Autoconf) 2.69
-] automake (GNU automake) 1.15
-] guile-2.0 2.0.12
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: 473 bytes --]
next reply other threads:[~2016-09-19 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 2:03 David Pirotte [this message]
2016-09-19 9:12 ` Guile-Lib 0.2.3 released Alex Kost
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=20160918230308.46a38a36@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).