From: Cyprien Nicolas <c.nicolas@gmail.com>
To: gentoo-lisp@lists.gentoo.org
Cc: "Andrey G. Grozin" <A.G.Grozin@inp.nsk.su>
Subject: Re: [gentoo-lisp] Re: SLOTting dev-scheme/guile
Date: Thu, 27 Sep 2012 12:18:21 +0200 [thread overview]
Message-ID: <506427ED.6060905@gmail.com> (raw)
In-Reply-To: <alpine.LRH.1.10.1209271404280.22792@star.inp.nsk.su>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrey G. Grozin wrote:
> TeXmacs cannot be compiled with guile-2, and there are no plans to
> change this (upstreem even considers switching to some other
> scheme implementation, but not to guile-2). Therefore, I have
> >=scheme-2 masked on my system. As long as 1.8 remains in the tree,
> slotting should be OK for TeXmacs.
Thanks for the feedback, I have opened bug 436400 [1] for this issue.
Feel free to add yourself in CC.
I'll work on patching the build system to require guile:12 in
dependencies, and use guile-1.8 binaries and similar stuff. I will not
assign the bug to you and sci@ before I have an acceptable solution to
discuss.
If you know other issues regarding guile-2, feel free to open bugs
assigned either to myself or scheme@.
Regards,
- --
Cyprien/Fulax
1: https://bugs.gentoo.org/show_bug.cgi?id=436400
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBkJ+0ACgkQWxOlHn1uWpdScgCcDm/ZRmF4HZ+KjNzOdAdyqaB1
zL0Anjd4BemyCPeKkdqu2LP1NpT67AXu
=Ek4d
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-09-27 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 13:10 [gentoo-lisp] SLOTting dev-scheme/guile Cyprien Nicolas
2012-09-26 21:06 ` [gentoo-lisp] " Cyprien Nicolas
2012-09-27 7:07 ` Andrey G. Grozin
2012-09-27 10:18 ` Cyprien Nicolas [this message]
2013-01-26 14:49 ` Cyprien Nicolas
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=506427ED.6060905@gmail.com \
--to=c.nicolas@gmail.com \
--cc=A.G.Grozin@inp.nsk.su \
--cc=gentoo-lisp@lists.gentoo.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