From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: 1.8 status
Date: Sat, 12 Aug 2006 16:00:39 -0700 [thread overview]
Message-ID: <87hd0h36g8.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: rmilkpw1r6x.fsf@fnord.ir.bbn.com
Greg Troxel <gdt@ir.bbn.com> writes:
> 1.8.0 seems to now be pretty old, and a diff of the head of
> branch_release-1-8 against release_1-8-0 (-Nu) gives 6088 lines, of
> which 2857 are new (ignorning hierarchy.pdf).
>
> The slib bug fix appears not to be present on the 1.8 branch, but I'm
> not quite sure - it seems only to be on the 1.6 branch, and not on
> HEAD.
Right. The problem is that things have changed in 1.8, and we still
haven't worked out the right way to handle SLIB. The solution will
almost certainly look a lot like the one in 1.6, but we also need to
make sure the upstream guile.init is appropriate for 1.8.
I've been talking with Aubrey Jaffer about this, but we've been going
fairly slowly.
The lack of SLIB support is one of the reasons that I haven't uploaded
1.8 packages for Debian yet. I was hoping to wait until we had gotten
that worked out, but I've decided to just go ahead, so I should be
uploading 1.8 packages within about a week or so.
> Is it currently reasonable to use 1.8.0? It seems there's been a lot
> of work on the branch, and that probably a 1.8.1 is in order.
I'm planning to release 1.8.0 in Debian, but I'll add patches when
they're needed. I will probably be fairly conservative, though. So
far, the only patch I know is going in is one to fix the numbers.test
failure.
> Does any know of any problems with any of them with 1.8? In
> particular, do gnucash and lilypond work with 1.8.0?
I think lilypond probably does.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-08-12 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 16:38 1.8 status Greg Troxel
2006-08-10 16:48 ` Bruce Korb
2006-08-10 23:06 ` Kevin Ryde
2006-08-12 23:00 ` Rob Browning [this message]
2006-08-13 23:44 ` Kevin Ryde
2006-08-14 17:22 ` Greg Troxel
-- strict thread matches above, loose matches on Subject: below --
2006-03-26 13:02 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=87hd0h36g8.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.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).