unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Massimiliano Gubinelli <m.gubinelli@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: rfc: next guile 1.8.x release
Date: Sat, 16 Jan 2021 17:55:22 -0500	[thread overview]
Message-ID: <874kjgpk4l.fsf@gnuvola.org> (raw)
In-Reply-To: <E18FFE3A-8DA5-4911-A881-6BD03179C1CD@gmail.com> (Massimiliano Gubinelli's message of "Tue, 12 Jan 2021 11:55:37 +0100")

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


() Massimiliano Gubinelli <m.gubinelli@gmail.com>
() Tue, 12 Jan 2021 11:55:37 +0100

   I was not aware that Guile 1.8 was still "officially"
   maintained. What is the current status/policy about it?

I believe the maintainers have stopped supporting Guile 1.8.x
for a while now.  I'm not an official maintainer, just someone
who has write privs for the repo.  I suppose it would be good to
hear from the official maintainers before proceeding, so as to
avoid any surprises, but my gut feel is that they're pretty
relaxed about anything that does not interfere w/ the cutting
edge stuff they do.

   I'm not sure is appropriate to ask but it would be nice if
   MinGW (both 32 and 64 bit) could be supported and to have it
   parallel installable with Guile 2 (and Guile 3).

I think it's always appropriate to express "it would be nice"
thoughts.  What can it hurt?

That said, i'm not familiar w/ MinGW, so i will rely on
community feedback to guide me.  As long as MinGW support does
not impede GNU/Linux functionality, i think we'll be fine...

-- 
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-01-16 22:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 21:54 rfc: next guile 1.8.x release Thien-Thi Nguyen
2021-01-11 14:51 ` Mike Gran
2021-01-12 10:55   ` Massimiliano Gubinelli
2021-01-16 22:55     ` Thien-Thi Nguyen [this message]
2021-01-16 22:48   ` Thien-Thi Nguyen
2021-01-29 21:35 ` Ludovic Courtès
2021-01-29 23:46   ` Dr. Arne Babenhauserheide
2021-01-30 12:31     ` Ricardo Wurmus
2021-01-30 14:49       ` Dr. Arne Babenhauserheide
2021-01-31 17:35       ` Massimiliano Gubinelli
2021-02-01 21:49         ` Ludovic Courtès
2021-02-07  6:59         ` John Cowan
2021-03-08 20:36 ` Andy Wingo
2021-03-09  7:14   ` Dr. Arne Babenhauserheide
2022-03-03  0:11     ` Thien-Thi Nguyen
2022-03-14 12:14       ` Thien-Thi Nguyen

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=874kjgpk4l.fsf@gnuvola.org \
    --to=ttn@gnuvola.org \
    --cc=guile-user@gnu.org \
    --cc=m.gubinelli@gmail.com \
    /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).