unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-sources@gnu.org
Cc: guile-user@gnu.org
Subject: Guile-PG 0.50 available
Date: Sat, 04 Dec 2021 20:35:00 -0500	[thread overview]
Message-ID: <871r2r96m3.fsf@gnuvola.org> (raw)

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


release notes:

  Woo hoo, "half"-way there!  :-D

  Let's hope we can reach 1.0 sometime this decade...

  Also, hackers may want to check out the Git repo, new dir xp/,
  for yet another way to push your multicore system to insanity.

README excerpt:

  Guile-PG is a collection of modules for Guile allowing access to
  the PostgreSQL RDBMS from Scheme programs.

  The low-level module ‘(database postgres)’ provides an almost
  one-to-one correspondence with the PostgreSQL "libpq" C library
  interface.  The other modules build on it to provide abstractions
  and convenience procedures.

NEWS for 0.50 (2021-12-04):

  - distribution now .tar.lz

    If you have GNU tar, you can use "tar xf" and it will DTRT.
    If not, you can use "lzip -dc TARBALL | tar xf -" to unpack it.

  - lob details bifurcated for "modern" Guile

    Guile 2.2 (and later, presumably) have ‘scm_c_make_port’ and in
    fact a whole rewrite of the ports extension mechanism.  Thus,
    all previous Guile-PG releases failed to build w/ Guile 2.2.
    Specifically, all the large object (lob) low-level details
    clashed irreconcilably.

    This release of Guile-PG now handles things by configure-time
    detection and selection of a suitably matching implementation.

    The file test/OK now includes an entry w/ a subheading of "other
    Guile" to show the range of supported Guile versions.  More to
    the point, if you build w/ Guile 2.2 and encounter problems,
    then please report it.

    NB: We haven't dipped into the Guile 3.0 waters yet.  Experience
    reports from those more adventurous are welcome, in any case.

  - bootstrap/maintenance tools

    upgraded:

     Guile-BAUX 20211106.0154.1368008
     GNU gnulib 2021-12-01 01:50:01
     GNU Autoconf 2.71
     GNU Automake 1.16.5
     GNU texinfo 6.8
     GNU Guile 2.2.7

    as before:

     (none)

tarball in dir:

  http://download.savannah.nongnu.org/releases/guile-pg/

homepage:

  https://www.nongnu.org/guile-pg/

donation:

  https://www.gnuvola.org/patronage/

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)               ; (2021) Software Libero
   (pcase (context query)               ;       = Dissenso Etico
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 219 bytes --]

                 reply	other threads:[~2021-12-05  1: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=871r2r96m3.fsf@gnuvola.org \
    --to=ttn@gnuvola.org \
    --cc=guile-sources@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).