[pkg-firebird-general] [long] firebird 2.0 - and now what?

[Damyan Ivanov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

I'd like to get firebird 2.0 release in etch. And I'd like your opinion
on this.

The problem is that there are known incompatibilities between 1.5 and
2.0 databases. A 2.0 server may have problems working with databases
created by 1.5 server. This leads to conclusion that 1.5 and 2.0 must be
both installable at the same time to allow migration of the data. My
plan is to have both 1.5 and 2.0 in etch and have only 2.x in etch+1.

The need to have both 1.5 and 2.0 in a release cycle urges to get them
together ASAP, since having 1.5 in etch+1 is something I'd like to avoid
- - 2.0 has much better features/codebase and is the right choice when
considering firebird database.

There are no backward-incompatible changes in the API so clients and
servers may be mixed freely.


Please comment on the following plan. I am not at all experienced in
complex transitions and I have surely overlooked something. There still
is time to get this done for etch.


Here is my plan:

New source package, firebird2-2.0 with following binary packages:
firebird2-2.0-super-server
firebird2-2.0-classis-server
firebird2-2.0-server-common
firebird2-2.0-common
libfbclient2
libfbembed2
firebird2-2.0-utils-super
firebird2-2.0-utils-classic
firebird2-2.0-dev

Here's what gets where:

* firebird2-2.0-super-server
the super-server binary, gsec, fbmgr, UDFs, initscript, libib_util.so
(in /usr/lib/firebird2-2.0)
+ depends on firebird2-2.0-server-common and firebird2-2.0-common

* firebird2-2.0-classic-server
fb_inet_server, fb_lock_mgr, gsec etc, xinetd sample config, UDFs,
libib_util.so
+ depends on libfbembed2, firebird2-2.0-server-common and
firebird2-2.0-common

* firebird2-2.0-server-common
default security2.fdb, instantiation scripts

* firebird2-2.0-common
content common to both servers and clients
/etc/firebird2-2.0/firebird.conf, aliases.conf, firebird2.msg (messages)
logrotate snipplet

* libfbclient2
libfbclient.so.2 --> libfbclient.so.2.0.0
+ depends on firebird2-2.0-common

* libfbembed2
libfbembed.so.2 --> libfbembed.so.2.0.0
+ depends on firebird2-2.0-common

* firebird2-2.0-utils-super
the usual tools in /usr/bin
+ depends on libfbclient2
+ replaces/provides firebird2-utils-super

* firebird2-2.0-utils-classic
the usual tools in /usr/bin
+ depends on libfbembed2
+ replaces/provides firebird2-utils-classic

firebird2-2.0-dev
header files,
libfbclient.so --> libfbclient.so.2.0.0
libfbembed.so --> libfbembed.so.2.0.0
libgds.so --> libfbclient.so.2.0.0 (compatibility with fb1.0)
+ depends on libfbclient2 and libfbembed2
+ replaces/provides firebird2-dev


** After firebird2-2.0 packages enter archive, the following packages
from firebird2 source become transitional:
firebird2-utils-super - depends on firebird2-2.0-utils-super
firebird2-utils-classic - depends on firebird2-2.0-utils-classic
firebird2-dev - depends on firebird2-2.0-dev

After this, a notification for all packages build-depending on
firebird2-dev shall be sent to correct B-D to firebird2-2.0-dev



That's it. I'd appreciate any response. Please prove I am not the only
one active on this list.


dam
- --
Damyan Ivanov                           Modular Software Systems
dam at modsoftsys.com
phone +359(2)928-2611, 929-3993              fax +359(2)920-0994
mobile +359(88)856-6067             dam at jabber.minus273.org/Gaim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEf3LHHqjlqpcl9jsRArj8AJ9kJ2jtRYoXUszVLF2x46hRgLCp7QCgktZU
zPumflFwQ2OkMDAKJmrekxg=
=q9YN
-----END PGP SIGNATURE-----