unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Guile 1.6.1 is available.
Date: Mon, 16 Dec 2002 00:39:20 -0600	[thread overview]
Message-ID: <87y96q5uxz.fsf@raven.i.defaultvalue.org> (raw)


We are pleased to announce the availability of a new Guile release.
This is the next maintenance release for the 1.6 stable series.

You can find it here:

  ftp://ftp.gnu.org/gnu/guile/guile-1.6.1.tar.gz.

Guile is Project GNU's extension language library, an interpreter for
Scheme, packaged as a library that you can link into your applications
to give them their own scripting language.  Guile should eventually
support other languages as well, giving users of Guile-based
applications a choice of languages.

Some highlights of the 1.6.1 release:

  - Guile now provide and uses an "effective" version number.

    Guile now provides scm_effective_version and effective-version
    functions which return the "effective" version number.  This is
    just the normal full version string without the final
    micro-version number, so the current effective-version is "1.6".
    The effective version should remain unchanged during a stable
    series, and should be used for items like the versioned share
    directory name i.e. /usr/share/guile/1.6.

    Providing an unchanging version number during a stable release for
    things like the versioned share directory can be particularly
    important for Guile "add-on" packages, since it provides a
    directory that they can install to that won't be changed out from
    under them with each micro release during a stable series.

  - Guile now uses it's own version of libltdl.

    Guile now uses its own modified version of libltdl (1.4.3) found
    in ./guile-libltdl which includes a variety of bugfixes and
    enhancements.  We auto generate patches against copies of the
    upstream source so it's easy to forward our modifications to the
    libtool developers.

  - The Emacs interface has been fixed.

  - The SRFI C headers are now installed.

See the NEWS file for further information about this release.

The Guile WWW page is located at

  http://www.gnu.org/software/guile/guile.html

It contains a link to the Guile FAQ and pointers to the mailing lists,
among other things.

This release is version 1.6.1.  Any bugs found will be addressed by
further bugfix releases numbered 1.6.2, 1.6.3, and so on.  The next
stable Guile release with significant functional improvements will be
version 1.8.0.

In between 1.6.x and 1.8.x, you can follow Guile development in CVS
and in the Guile mailing lists (see ANON-CVS and HACKING).  Guile
builds from the development branch of CVS will have version number
1.7.0.

Guile versions with an odd middle number, i.e. 1.5.* are unstable
development versions.  Even middle numbers indicate stable versions.
This has been the case since the 1.3.* series.

Please send bug reports to bug-guile@gnu.org.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


                 reply	other threads:[~2002-12-16  6:39 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=87y96q5uxz.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.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).