[Firebird-devel] Debian's FB package split (confirmations, opinions please)

[Grzegorz P. <gr...@se...>]

Hi!

As FB package aparently won't go into woody I can turn the current
version upside down. Among other small things there's one huge, which
I was thinking of for some quite long time: package split.

Here's the proposal, plese comment and confirm or disagree with what
is written below...

				Grzegorz Prokopski


Here's proposal of how I imagine firebird package split.
Thanks to Damyan Ivanov for reminding me about this writing the idea
down and other help.

Short proposal (written by Damyan Ivanov):
Separate package for examples 'firebird-examples'.
 - contains the examples directory. inst
Separate package for development files 'firebird-dev'
 - contains include/ stuff
Separate package for Firebird library 'libfirebird64', 'libfirebird32'
 - contains libgds. provide libfirebird
Separate packages for client, server-classic and server-super.
 - firebird-client does not containg anything by itsels, just depends on
   libfirebird to get libgds
 - firebird-server-classic contains gds_inet_server plus inetd
   configuration
 - firebird-server-super contains ibmgr and ibsrv (or what is the name
   in super) plus init.d scripts
Separate package for the tools 'firebird-util'
 - contains all other things from bin/ - gbak gfix etc.
Separate package for documentation (when one is available)
 - firebird-doc


More information - dirs and files (written by Grzegorz Prokopski)

(fb -> firebird, $INTERBASE -> /usr/lib/firebird)

* firebird-examples
content - as of original /opt/interbase/examples
Problem is that there are *.gbk *.gdb *.sql *.c *.h *.e - MESS! ;-)
Where should be which of them?
maybe move: *.gbk *.gdb *.sql to /var/lib/firebird/examples (together)
but what about the rest? - don't know may be:
/usr/share/doc/firebird-examples/( c | code )
Another problem is that some tools may want to access
all those examples at $INTERBASE/examples (TCS for ex., but
I think about commercial closed source things).

So maybe just put all to /var/lib/fb/examples an symlink
from $INTERBASE/examples ?
when it's separate package - simply nobody will install it ;-)

* firebird-dev
content - as of original /opt/interbase/include
now it goes to /usr/include
BTW: is the gds.f useful for anything?
Depends: libfirebird

* libfirebird
content - as of original /opt/interbase/lib
It seems that libs (libgds.so.0, libib_util.so)
differ only between 32 and 64 but not between super and classic
(confirmation from developers would be nice here)
so two packages: libfirebird32 and libfirebird64
Provides: libfirebird (on this other packages should depend)
BTW: is the libgds.a file needed for ANYTHING?

* firebird-utils (or -tools?)
content - part of original /opt/interbase/bin
now in /usr/bin:
gbak, gdef, gfix, gpre, gsec, gstat, isql, qli
gsplit seems to differ between 32 and 64 bit versions
so it won't be included here
(confirmation from developers would be nice here)
Depends: libfirebird

* firebird-server-common
/intl/gdsintl
interbase.msg
Plese explain: what exactly is gdsintl used by? only by FB server?

* firebird-(c|s)(32|64)-server (4 packages)
content - "the rest"
not every file in the package are really specific
for classic x super x 32bit x 64bit
but I don't want another 4 packages even IF those 4 could be
then on those additional ones.
Depends: firebird-server-common, libfirebird
Recommends: (Suggests:?) firebird-utils (or -tools)

* firebird-doc
content - none atm, only a note where one can get the docs and
explaination why none is included in the package.

NOTES
* huh - it makes total of 10 binary packages ;-) nice... thanks God
for the apt.
* I omitted firebird-client as I think client programs will simply
depend on the library. I cannot see any useful fb-client files ATM.
* some package has to contain /etc/firebird/firebird.env. this file
carries information about how INTERBASE and (eventually) other
variables are set. It is used by fb-server but I am not sure
if fb-utils wouldn't need it too? ATM firebird-server-common seems
to be good place for it, and the rest of /etc/ stuff.
One should be able to easily switch between server flavours without
the need of reconfiguration. We'll see.
* /usr/lib/firebird should be created only by firebird-utils.
The inside symlinks to files from other packages should also be carried
by this package
* after inclusion of FB into main PHP maintainer should be noted that
he can add interbase module (and another dependency ;-)