Clark Jones writes:
> Dave Peticolas wrote:
> >
> > Clark Jones writes:
> > > Developers:
> [...]
> > > I would suggest that whoever's the keeper of the "makefile" that's used f
> or
> > > the RPM please consider looking to see if you can't chop off the ".4" on
> > > libguile.so and the ".3" on libreadline.so so that we can use the "generi
> c"
> > > softlinks.
> [...]
> > The problem is one we're really not supposed to work around. As I
> > understand it, the idea behind changing the library major version is
> > that it is *supposed* to break backwards compatibility, because the
> > library developers have decided that the api has changed enough that
> > backwards compatibility cannot be supported.
> >
> > In the guile case, it seems that "fooling" the system into using the
> > new library with a soft link will still work, but in general it's not
> > something we should be doing automatically.
>
> The guile package itself plants soft links for major versions 3, 5, and 6,
> all pointing to 6.0.0. (The GnuCash problem seems to be arising from the
> fact that it isn't planting one for version 4. To me, this suggests that
> major version 4 had some major muck-up, and shouldn't be used at all...)
>
> > The correct way to solve this problem would be to build a binary package
> > on a mandrake system, and have mandrake users use that instead. Ditto for
> > SuSE, etc.
>
> Unnecisarily linking to a specific version will still be a problem. If there
> is a good reason for tying to a specific version of a given library, then
> it seems to me that the particular version of the library in question should
> be copied to the application (in this case, GnuCash's) download area, to
> assure its continued availability. I have yet to find sources for guile 4,
> let alone an RPM (but since it works fine with 6, I've quit trying, and never
> did try too hard -- I probably could have if I'd wanted to badly enough).
Library version 4 is from guile-1.3.0. Linking to a specific major
version is how linking is done -- I'm not aware of any other way to do
it. Providing multiple versions in a single package is up to the guile
package, not gnucash.
As long as we build our packages on standard distributions, then
there won't be a problem, unless a user has upgraded their libraries
to incompatible versions. But if you're doing that, then you're on
your own anyway.
dave
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
