Re: g-wrap parallel installability part deux

[Greg Troxel]

> From: Andreas Rottmann <address@hidden>
> Date: Thu, 07 Oct 2004 19:58:39 +0200
> In-Reply-To: <address@hidden> (Greg Troxel's message of
>  "07 Oct 2004 12:51:11 -0400")
> Message-ID: <address@hidden>

> Yes, it's true that the new g-wrap isn't a drop-in replacement, even
> with the compat layer, which is pretty complete now (I was able to
> build GnuCash with it), since it doesn't support GLib 1.2. I'm
> thinking about changing that and ship a GLib 1.2 wrapper, but I'm
> somewhat hesistant due to the code duplication this involves.

As long as it can be installed in parallel -- with any packaging
system -- which I think implies a different name, e.g. gwrap2, it's
fine not to be compatible.  But the old one will live a long time.

> Hmm, can't do much about that; if I get the new g-wrap to support GLib
> 1.2, maybe the netbsd pkgsrc should be updated.

>From the pkgsrc point of view, the new g-wrap would get a g-wrap2
package, and one could install both.  autoconf213 and autoconf (2.59
or so) are like this, as is gtk and gtk2.   Then installing GnuCash
would build the old one, and guile-gnome the new one, and all would be
well.
My point really is that it is unworkable to expect everything to
switch, and if it isn't _really_ compatible, then both will have to
coexist for a long long time, until all programs that use it have been
updated.  Perhaps 2 years.

> Well, the arch thing shouldn't keep you from trying - there are
> recent tarballs of both G-Wrap and guile-gnome available.

I have seen that on the list, and will try again - I'm also low on
Copious Spare Time.

But, according to

  http://home.gna.org/guile-gnome/download/

they aren't tarballs :-), and I don't see anything on the developer page
either.  Even if the download link were just a server-generated page
with what's in the directory it woudl be nicer for the casual user.

I don't mean to sound too complaining - I think this is cool stuff and
really would like to see it succeed.  I just want to give the
perspective of someone doing package system maintenance who's removed
from the fray.