From: Andy Wingo <wingo@pobox.com>
To: guile-gtk-general <guile-gtk-general@gnu.org>,
guile-user <guile-user@gnu.org>
Subject: [ann] guile-gnome-platform 2.15.98 released
Date: Fri, 25 Apr 2008 15:35:31 +0200 [thread overview]
Message-ID: <m3k5imys4c.fsf@pobox.com> (raw)
Greetings, disciples of Lambda: The Ultimate Cult,
I am pleased to announce the release of guile-gnome-platform version
2.15.98.
guile-gnome-platform 2.15.98 may be downloaded from:
http://ftp.gnu.org/pub/gnu/guile-gnome/guile-gnome-platform/guile-gnome-platform-2.15.98.tar.gz
About guile-gnome-platform
==========================
guile-gnome-platform is a binding between Guile Scheme and the Gnome
stack of libraries.
This release is a part of the unstable 2.15 series, which aims to wrap
the libraries in the Gnome Developer Platform at version 2.16. It is
unstable, but 2.16.0 will be stable.
guile-gnome-platform 2.15.98 is a preview for 2.16.0. If everything goes
right, something very close to this release will be pushed as 2.16.0
within a couple weeks.
For that reason, it's *very important* to test this one as widely as
possible, because hopefully we can get some nice buzz about the upcoming
stable release, and it would be good if we caught and fixed any problems
before they turn into someone's first impression.
The so-called API_VERSION of guile-gnome has been bumped to 2 (from 0),
so your code will need to "link" to it that way. See the glib notes for
more details.
Changes
=======
packaging changes
-----------------
* Formally require Guile 1.8, as has been the case for a while now.
* Bump the API_VERSION to 2, as a test before going stable.
This will change all library names, pkg-config names, installed header
names, etc. (use-modules (gnome-0)) in user code should be changed to
(use-modules (gnome-2)). guile-gnome-0 is now guile-gnome-2.
The purpose of this change is to shake out any bugs in the API_VERSION
mechanism. The intention is for the next release to be 2.16.0, with
API_VERSION=2.
atk
---
* Documentation updated.
cairo
-----
* New platform release, no change.
corba
-----
* New platform release, no change.
defs
----
* New platform release, no change.
docs
----
* New platform release, no change.
gconf
-----
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
glib
----
* API changes: Made gtype-interface-destroy! public. Removed the
terrible %especify-metaclass! as it is not used.
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
* A few bugfixes after the large changes in 2.15.97.
gnome-vfs
---------
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
gtk
---
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
* Remove special wrapper for <gtk-message-dialog>, as GTK+ 2.10 has
enough of a gobject property interface.
libglade
--------
* Documentation updated.
libgnome
--------
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
libgnomecanvas
--------------
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
libgnomeui
----------
* Documentation updated.
pango
-----
* Documentation updated.
* Don't use API deprecated in Guile 1.8.
Peace,
Andy
--
http://wingolog.org/
reply other threads:[~2008-04-25 13:35 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=m3k5imys4c.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-gtk-general@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).