From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Release now?
Date: Thu, 27 Feb 2003 15:47:06 -0600 [thread overview]
Message-ID: <87lm01jt0l.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <rmin0khzbpc.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "27 Feb 2003 15:54:23 -0500")
Greg Troxel <gdt@ir.bbn.com> writes:
> {list: I have received no hate mail for ranting so I presume this is
> welcome; feel free to tell me otherwise!}
Well I'm interested, so don't worry about it :>
> There are 2 parallel worlds, one rooted on glib 1.2, and one on
> glib-2.0. This indeed doesn't scale, but it's the underlying
> interface changes that break compiling that don't scale. But it
> isn't quite that bad, since in the guile world one would have the
> last guile-gtk version that worked with guile 14, and one that works
> with 16. Then there is gnome-guile that does glib2/gtk2/ORBit2, and
> probably that would be built for the new guile only.
Ahh, ok, thx. One of the more aggravating questions which we've
already discussed to death here and on debian-devel, is how do I
handle allowing people to build the current version of g-wrap for
either guile 1.4 or guile 1.6 -- i.e. unless I embed the guile version
in g-wrap's libs' names (or the sonames), then there's no way to pick
a "correct" soname.
> Perhaps this is all a red herring and we can preserve compile-time
> compatibility adequately. Keeping the old libs around seems to be a
> good solution for running old binaries. In the specific case of
> Gnucash, what about 1.6 made gnucash 1.6.8 not buildable, and was that
> something that wasn't deprecated in 1.4? We may be solving the wrong
> problem.
AFAIK gnucash just needed to be ported/updated. I actually did that
work some time back for another project, but I don't think I preserved
the ability to use both guile 1.4 and guile 1.6, and at the time I
believe that would have been a problem. I haven't been involved much
with gnucash lately, so I don't know where they actually stand on that
front, and unfortunately I don't think I have those changes anymore.
However, as far as I recall, I got gnucash working fine with guile
1.5.X.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, 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://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-02-27 21:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 12:37 Release now? Mikael Djurfeldt
2003-02-24 13:08 ` Dale P. Smith
2003-02-24 13:21 ` Mikael Djurfeldt
2003-02-24 13:32 ` Greg Troxel
2003-02-25 13:34 ` Marius Vollmer
2003-02-25 16:08 ` Greg Troxel
2003-02-25 18:38 ` Rob Browning
2003-02-26 1:51 ` Greg Troxel
2003-02-26 2:27 ` Rob Browning
2003-02-27 14:25 ` Greg Troxel
2003-02-27 15:21 ` pkg-config support for guile Greg Troxel
2003-03-22 23:31 ` Marius Vollmer
2003-04-23 21:22 ` Greg Troxel
2003-05-16 23:21 ` Marius Vollmer
2003-02-27 16:54 ` Release now? Rob Browning
2003-02-27 18:07 ` Greg Troxel
2003-02-27 18:45 ` Rob Browning
2003-02-27 19:25 ` Greg Troxel
2003-02-27 20:14 ` Rob Browning
2003-02-27 19:06 ` Rob Browning
2003-02-27 19:13 ` Rob Browning
2003-02-27 19:36 ` Greg Troxel
2003-02-27 20:02 ` Rob Browning
2003-02-27 20:54 ` Greg Troxel
2003-02-27 21:07 ` Dale P. Smith
2003-02-27 21:30 ` Dale P. Smith
2003-02-27 21:47 ` Rob Browning [this message]
2003-04-25 19:26 ` Neil Jerram
2003-02-25 16:28 ` Andreas Rottmann
2003-02-24 18:35 ` Rob Browning
2003-02-25 13:20 ` Marius Vollmer
2003-03-03 14:06 ` Mikael Djurfeldt
2003-04-25 19:28 ` Neil Jerram
2003-04-25 22:59 ` Marius Vollmer
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=87lm01jt0l.fsf@raven.i.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).