From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: how to manage 2 guile version
Date: Tue, 28 Mar 2017 16:01:00 -0000 [thread overview]
Message-ID: <491246ce-7dff-f1f1-5ffc-9545ec8e282f@cygwin.com> (raw)
In-Reply-To: <20170328071146.GE1836@debbie.mshome.net>
On 2017-03-28 02:11, szgyg wrote:
> FWIW guile 2.2.0 was released two weeks ago [0]. Mostly works, but it
> still has failing tests [1].
Oh, great...
So we probably should take this into consideration *now*, even though
most guile consumers aren't ready for the changes in 2.2 yet.
Fortunately, it seems guile itself has taken their own instability into
account:
https://www.gnu.org/software/guile/manual/html_node/Parallel-Installations.html
Although looking at packages which use guile, most haven't fully adapted
to this yet (guile-config is still used by some, and it doesn't seem
anyone is using pkg-config to find guile and guild), so we still need to
provide unversioned binaries/scripts in /usr/bin for now.
It's way too early to make 2.2 "the" guile, so I think we stick with a
versioned guile1.8 for the stragglers, and 'guile' being 2.0 for now,
but eventually transitioning to a versioned 'guile2.0'. We'll have to
take another look at this once the real world has adapted to 2.2.
--
Yaakov
next prev parent reply other threads:[~2017-03-28 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 20:13 Marco Atzeri
2016-07-14 21:29 ` Yaakov Selkowitz
2016-07-17 17:02 ` Marco Atzeri
2017-03-28 2:16 ` Yaakov Selkowitz
2017-03-28 5:50 ` Marco Atzeri
2017-03-28 7:09 ` szgyg
2017-03-28 16:01 ` Yaakov Selkowitz [this message]
2017-03-28 19:50 ` Marco Atzeri
2017-03-28 21:19 ` Yaakov Selkowitz
2017-03-28 15:34 ` Yaakov Selkowitz
2017-03-28 16:01 ` Marco Atzeri
2017-03-28 16:08 ` Yaakov Selkowitz
2017-04-01 12:30 ` Marco Atzeri
2017-04-03 2:07 ` Yaakov Selkowitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491246ce-7dff-f1f1-5ffc-9545ec8e282f@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.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).