[fpc-pascal] Re: linux: shouldwehard-codeversionedorunversionedshared libraries in our apps?

Reinier Olislagers reinierolislagers at gmail.com
Thu Aug 16 23:56:58 CEST 2012

On 16-8-2012 23:41, Graeme Geldenhuys wrote:
> Hi Reinier,
> On 16 August 2012 22:25, Reinier Olislagers <reinierolislagers-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>> Presumably the sqldb would be changed for the v3 library then?
> Yes, but that will only be in Trunk, and could take up to a year
> before the next FPC "stable" release. I only deploy my commercial apps
> with stable FPC releases. In the mean time Linux distros get released
> about twice a year now. So distros will be ahead of FPC, and during
> that time libfbclient.so could be point at a version our software (and
> FPC) doesn't support. I hope that makes it clear now.
It's been clear to me all along. That's the problem Marco was warning about.
The alternatives have been discussed ad nauseam as well.

>> Regardless, as mentioned, the Firebird services API allows you to find
>> out what version a server is running.
> Yes, but as someone else also did the same thing as you. You are
> jumping the gun. You assume a database connection can be established.
> My problem was that the app can't even run because the libfbclient.so
> is missing in every standard Linux install, and that symlink is not
> included in the standard Firebird Client library package.
No, here you were not talking about library not found/db connection not
established scenarios. Read your earlier posts above.
Seen e.g.:
>> fbclient.so should not be searched. It could point to anything, including versions of the library not supported by the unit.
> @Michael
> I have to agree with Jonas here. The unversioned symlink is potential
> trouble. Other than that, your solution sounds fine.
So a library (perhaps "including versions of the library not supported
by the unit") would already be loaded.

Anyway, that is still irrelevant. The problem of various versions of FB
clients and servers with different capabilities still needs to be addressed.
The simple solution would be to just only support the latest version for
both of them. Would that be enough? Who knows.

Personally, I don't really care anymore anyway. I'm just a hobby
programmer anyway.
I'm sure Michael will do a good job with his db changes and I'll leave
it to people like you who have production code running to submit patches.

Good luck,

More information about the fpc-pascal mailing list