Bug#251458: [Pkg-firebird-general] Bug#251458: Plan to get firebird, firebird2 and php4-interbase working in sarge.

[Damyan Ivanov]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDB482F7C5AB73A2CD19F7537
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Remco Seesink wrote:
> To get out of this mess for sarge I am packaging firebird1 libs without
> the server so the current linking situation in sarge which has been tested
> for a long time can be kept. That is php4-interbase (4.3.6-1) linked against
> libfirebird1. This works with the new version of firebird and has an added
> bonus of being backwards compatible with unofficial 1.0.x firebird packages.
> 
> This will solve all bugs #251458, #268931 and #255471. 

Can libfirebird1 co-exist with libfirebird2-* ? My impression was that 
libfirebird2-* replace/provide/conflict with libfirebird1. If I am 
correct, php4-interbase 4.3.6 would be uninstallable if libfirebird2-* 
in installed. I see that in this case php4-interbase will be 
uninstallable only on systems with firebird2-server installed. If your 
server is on ona machine, and your web server - on another this shall be 
no problem. For development, however, it is not uncommon to put 
everithing on one machine - firebird2-server (with libfirebird2) and 
apache (with php4-interbase).

On the other side, you may have in mind only build-depends on 
libfirebird1 and depends on libfirebird (generic, provided by both 
libfirebird1 and libfirebird2), in which case things may actually work :-)

> php4-interbase 4.3.8 packages in unstable will be rebuild against libfirebird1
> instead of libfirebird2 and when they really look stable be allowed in sarge
> if we didn't freeze by then.

> After sarge a more permanent solution for the problem can be worked out and
> the firebird1 packages can then be dropped.

Can the alternative system be used for this? I.e. we have two 
alternatives for libfirebird2 - "-classic" and "-super". They can't both 
be installed simultaneously, and they both provide the same API.

So php4-interbase can depend (and build-depend) on libfirebird2, which 
is provided by either libfirebird2-classic or libfirebird2-super.

The key point is to make php4-interbase link agains the "alternative 
alias". Currently, 3.6.1 is linked against libgds (provided by 
libfirebird1), which became a compatibility symlink in libfirebird2. 
This is just fine, but I can't imagine how to do it when building 
against libfirebird2 :-|

I am not sure if "alternative" has to be replaced with "diversion" 
above. I am not fluent with both alternative and diversion systems.


Hope this gives some food for thought.


dam

-- 
Damyan Ivanov                             Creditreform Bulgaria
divanov@creditreform.bg             http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993           fax: +359(2)920-0994
mobile: +359-88-856-6067      ICQ: 3028500      Y!M: dam3028500

--------------enigDB482F7C5AB73A2CD19F7537
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)

iD8DBQFBOCMCHqjlqpcl9jsRAlFGAKCAsavYN/oeNqgyaE+VEbbwO1f9VACdHaLO
5Kp/yzHF/49HrZbcl1u202I=
=SoPk
-----END PGP SIGNATURE-----

--------------enigDB482F7C5AB73A2CD19F7537--