Guile-Lib 0.2.6 released

[David Pirotte]

Hello,

We are pleased to announce Guile-Lib 0.2.6. This is a maintenance release, 
fixing
the default installation locations, and adding a new configure option - see 
below
for a complete description of these changes.


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

Here is a summary of the changes since version 0.2.5.1. 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.

** Installation location changes

The default and --prefix installation locations for source modules and
compiled files has been changed, and, in the absence of the new
configure option described below, are now:

  $(datadir)/guile-lib
  $(libdir)/guile-lib/guile/$(GUILE_EFFECTIVE_VERSION)/site-ccache

In the above, $(datadir) is substituted to the default /usr/local/share
or /your/prefix/share and $(libdir) is substituted to /usr/local/lib or
/your/prefix/lib, when/if --prefix was passed.

$(GUILE_EFFECTIVE_VERSION) is substituted to the stable version number
with which Guile-Lib is being compile, for example, 2.2

This change makes Guile-Lib compatible with the GNU Coding Standards,
but it also implies that, unless you use the new configure option
describe below, you will have to augment both Guile's variables
%load-path and %load-compiled-pat (see 'Environment Variables'
in Guile's Reference Manual) before to use Guile-Lib's modules.

** New configure option

The configure option --with-guile-site has been added, used to
explicitly ask Guile-Lib's source modules and compiled files to be
installed using Guile's global site and site-ccache directories
respectively.

It will only be honored if (and only if) it is passed as:

  --with-guile-site=yes

  [ in this case, there is obviously no need to augment Guile's
  [ variables %load-path and %load-compiled-path

The configure step now also lists the following variables: prefix,
exec_prefix, datarootdir, sitedir and siteccachedir.  It will also warn
the user if the last two variables differ from Guile's site and
site-ccache values.


* 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.3.22-c811-dirty


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.

pgpW4ZEsFgq48.pgp
Description: OpenPGP digital signature