Bug#251458: [Pkg-firebird-general] Bug#251458: Plan to get
firebird, firebird2 and php4-interbase working in sarge.
Damyan Ivanov <email@example.com>, firstname.lastname@example.org
Fri, 03 Sep 2004 13:11:34 +0300
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=us-ascii; format=flowed
I am thinking about the long term solution... and the best thing I've
rename the library to libfirebird2-classic (with all the .0, .so.0's)
and provide *hardlinks* named libfirebird2 (with all the .0 and .so.0's
rename the library to libfirebird2-super (ditto for .0 and .so.0's)
and provide *hardlinks* named libfirebird2 (ditto)
libfirebird2-* should conflict with each other and provide libfirebird2.
This way, any package compiled against either of them will link against
libfirebird2, not against libfb(client|embed)
Now that I write this, I am wondering, ain't it possible to rename the
library to libfirebird2 in both packages? This way there will be no need
of any ugly hardlinks.
All packages, depending on libfirebord2-* must be recompiled, of course,
and made link with libfirebird2. These are firebird2-server-* and
php4-interbase. All three of these are yours, so there's no need to
bother other maintainers :-)
Also, php4-interbase can build-depend and depend just on libfirebird2
(provided by -classic and -super).
What do you think?
Damyan Ivanov Creditreform Bulgaria
phone: +359(2)928-2611, 929-3993 fax: +359(2)920-0994
mobile: +359-88-856-6067 ICQ: 3028500 Y!M: dam3028500
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
-----END PGP SIGNATURE-----