From: Bruce Korb <bkorb@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: RFD: drop the GH interface.
Date: Thu, 18 Sep 2008 08:04:57 -0700 [thread overview]
Message-ID: <48D26E19.5000301@gnu.org> (raw)
In-Reply-To: <871vzhho7c.fsf@gnu.org>
Ludovic Courte`s wrote:
> Hi,
>
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
>> Do we have a consensus?
>
> Yes, fine by me, but no rush. ;-)
From a Guile-user and not developer perspective, the sequence needs to be:
1. the most retrograde platform must have all the GH capabilities in
the SCM interfaces for their releases. It seems to take quite a few
years for BSD to get around to building newer versions.
2. Once that happens, a couple of years must pass
3. I finally get around to removing GH stuff from my code (is there a guide?)
4. a couple more years pass
5. now it's okay by me for released code to not have GH.
I think we're to step 3 now, but I need to check the Guile version distributed
with net/open/free BSD. Last I looked (~4 or 5 years ago...), it was either
1.4.x or, perhaps, 1.6.x. It was many years behind. In any case, I would
suggest checking with your "customers" and "redistributors" instead of this list.
IMHO, anyway.
Regards, Bruce
next prev parent reply other threads:[~2008-09-18 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 3:08 RFD: drop the GH interface Han-Wen Nienhuys
2008-09-13 10:05 ` Ludovic Courtès
2008-09-14 16:19 ` Neil Jerram
2008-09-14 18:29 ` Han-Wen Nienhuys
2008-09-18 5:37 ` Han-Wen Nienhuys
2008-09-18 8:07 ` Ludovic Courtès
2008-09-18 9:07 ` Neil Jerram
2008-09-18 13:37 ` Ludovic Courtès
2008-09-20 23:11 ` Han-Wen Nienhuys
2008-09-28 20:47 ` Han-Wen Nienhuys
2008-09-28 20:58 ` Ludovic Courtès
2008-09-18 15:04 ` Bruce Korb [this message]
2008-09-19 21:57 ` Greg Troxel
2008-09-21 9:40 ` Neil Jerram
2008-09-21 18:02 ` Bruce Korb
2008-09-22 15:16 ` Ludovic Courtès
2008-09-22 20:12 ` Neil Jerram
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=48D26E19.5000301@gnu.org \
--to=bkorb@gnu.org \
--cc=guile-devel@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).