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-WWW 2.40 available
Date: Mon, 15 May 2017 14:55:21 +0200	[thread overview]
Message-ID: <87d1bauvnq.fsf@zigzag> (raw)

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

release notes:

  2017.  Finally, a default text/* "charset"!  Sizzweb will be happy.

  This release *almost* works w/ (Unofficial) Guile 1.4.1.128
  (test x300 fails due to a botched 2009 "drain input" refactor, sigh).
  However, it builds and passes "make check" w/ Guile 1.8.7, 1.8.8 and
  2.0.11 (w/ ‘GUILE_AUTO_COMPILE=0’).  Build reports for 2.2.x welcome!

  I will spew on the "documentation more spacious" NEWS item
  somewhere under <http://www.gnuvola.org/u/>, shortly.

  thi

README excerpt:

  This is the Guile WWW library, a set of Guile Scheme
  modules to facilitate HTTP, URL and CGI programming.

NEWS for 2.40 (2017-05-15):

  - 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.

  - configure DTRT w/ ‘GUILE’, ‘GUILE_CONFIG’, ‘GUILE_TOOLS’

    The configure script now recognizes, remembers and propagates
    through the build system, the vars ‘GUILE’, ‘GUILE_CONFIG’ and
    ‘GUILE_TOOLS’, expressed either as an env var:

     GUILE='guile-2.0 --no-auto-compile'
     export GUILE
     ./configure

    or (preferably) as an arg to configure:

     ./configure GUILE='guile-2.0 --no-auto-compile'

    As shown here, the var value need not be an absolute filename
    (although that doesn't hurt), and can include options.

    If your system has multiple Guile interpreters installed, to
    avoid horrible confusion, it's probably a good idea to specify
    either all three vars together, or none of them.

  - new support for ‘make describe’

    See (new) file ‘v/README’ for details.

  - new facility to elaborate ‘text/*’ MIME type

    Module ‘(www server-utils filesystem)’ now provides fluid
    ‘default-text-charset’ and proc ‘fully-specified’.  You can use
    these to elaborate a naked ‘text/*’ MIME type w/ charset info.
    For example:

     (with-fluids ((default-text-charset "UTF-8"))
       (list (fully-specified 'type "image/jpeg")
             (fully-specified 'type "text/plain")
             (fully-specified 'Content-Type "text/plain")))
     =>
     ((type "image/jpeg")
      (type "text/plain" charset "UTF-8")
      (Content-Type "text/plain;charset=UTF-8"))

    This facility is in module ‘(www server-utils filesystem)’
    rather than module ‘(www data mime-types)’ to keep it near
    ‘filename->content-type’.

  - portability tweaks

    Both forward and backward in time, we slog.

  - documentation more spacious

    For improved readability, the Info format of the documentation
    now sports thirteen more blank lines than before.

  - bootstrap tools
    - upgraded
      - GNU Texinfo 6.3
      - Guile-BAUX 20170509.0757.4f8084b
    - as before
      - GNU Autoconf 2.69
      - GNU Automake 1.15

download directory and files:

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

  77cb65a908da432a4d9a33643153d021  guile-www-2.40.tar.lz.sig
  1c2e045af35052be4be321e33caf9c35  guile-www-2.40.tar.lz

home page:

  http://www.nongnu.org/guile-www/

tip jar:

  http://www.gnuvola.org/patronage.html

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

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

                 reply	other threads:[~2017-05-15 12:55 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=87d1bauvnq.fsf@zigzag \
    --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).