public inbox for gentoo-lisp@lists.gentoo.org
 help / color / mirror / Atom feed
From: Cyprien Nicolas <c.nicolas@gmail.com>
To: Gentoo-Lisp Mailing list <gentoo-lisp@lists.gentoo.org>
Subject: [gentoo-lisp] Re: SLOTting dev-scheme/guile
Date: Wed, 26 Sep 2012 23:06:10 +0200	[thread overview]
Message-ID: <50636E42.3090203@gmail.com> (raw)
In-Reply-To: <4E5E32DE.6040501@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Cyprien Nicolas wrote:
> Hello fellows,
> 
> I just pushed to our overlay [1] an update to three guile ebuilds
> in order to support SLOTs via app-admin/eselect-guile, which was
> pushed along.

It has been more than a year now, and things have changed :-)

I've been using SLOTed guile since then, and I didn't notice a lot of
issues. Some of them has been fixed and pushed either in the ebuild or
into eselect-guile.

> Current issue with guile-2.0.1 haven't changed, they were reported
> by Marijn in package.mask: # - Broken emacs support (ulm has
> promised to look)

emacs support is actually not broken, it is simply not provided by the
distribution tarball for guile-2. It was a debugger for guile-1.8
which is not usable as the internal changed a lot between those two
releases. So I just removed any emacs related things in guile-2.0.x
ebuilds.

> # - doesn't build when boehm-gc is built without threads

I cannot reproduce anymore the build failure related to threads with
guile-2.0.6, I haven't test with guile-2.0.5. It seems this has been
fixed somehow.


So we have good news, guile can now be shipped to everyone, as all
major issues have been fixed. I'm planning to unmask guile-1.8.8-r2,
guile-2.0.6 and eselect-guile-1.0 during the next week-end for
enabling full testing for guile overlay users.

After a month or so, I think we will be able to push it to the main
tree :-)


There is still bug 351991 [1] concerning dev-scheme/greg. The only use
of greg in the tree is for running tests of sci-chemistry/coot. I
assigned the bug to sci@ herd 3 days ago, so I think it will get
adresses in the upcoming weeks.


Thanks for your interest in the Gentoo Lisp project,

- -- 
Cyprien / Fulax on #gentoo-lisp

1: https://bugs.gentoo.org/show_bug.cgi?id=351991

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBjbkIACgkQWxOlHn1uWpf1LQCdEB73qOlS8DvdQiBRmoQHUdUF
7nAAni3abbvBUTUZSbuhTlW693M+gUMg
=y0wP
-----END PGP SIGNATURE-----


  reply	other threads:[~2012-09-27  0: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 ` Cyprien Nicolas [this message]
2012-09-27  7:07   ` [gentoo-lisp] " Andrey G. Grozin
2012-09-27 10:18     ` Cyprien Nicolas
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=50636E42.3090203@gmail.com \
    --to=c.nicolas@gmail.com \
    --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