1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
AOLserver for DEBIAN -- the obscure side
----------------------------------------
This document explains some aspects of AOLserver that should be considered for
developer and packager of third-parties modules. The AOLserver set of modules
is not thought to be used in a multi-versioned Tcl/AOLserver environment.
To cope with that and avoid misterious problems (aka sudden seg faults at run
time) you have to ensure that all modules are built within the same environment,
i.e. the same Tcl version and the same AOLserver version. This is quite
difficult to get using independent binary packages such as those enclosed
in Debian GNU/Linux.
This is the tricky aspect: each aolserver4 provides an aolserver4-core-<AOLVER>-<AOLABI>
package and all modules have to depend on that at the time of building.
So currently all aolserver4-ns* module have to depend on aolserver4-core-4.5.1-0
for instance. Every time a new Tcl major release becomes available (with
possible ABI breakages at C library level) and AOLserver is compiled
against it, tha AOLABI version increases, and that prevents any old
module to be used with the new server. At that time ALL modules needs to
be re-built to ensure internal coherence.
The -dev package provides a /usr/share/aolserver4/debian.substvars
file which can be used as deb-substvars(5) snippet for adding the right
set of dependencies for modules in a ${aolserver:Depends} variable. This
should be the preferred and more direct manner to support versioned
interfaces. Thanks Sergei Golovan for suggesting this technique.
Happy hacking
-- Francesco P. Lovergine <frankie@debian.org> Wed Jun 17 15:25:13 CEST 2009
|
