As I've been saying for a while, we should ship Inkscape bound -statically- to the C++ libs we need, so that there will not be a dependency on -them-. The binary will be larger, of course, but the memory footprint would be the same as when you launch dynamically-bound Inkscape, and the C++ .so's need to be loaded. Our problem would be with how the C++ libs work with the corresponding Gtk libs. But this would be the same as how Inkscape would depend on Gtk, anyway. This also helps to save us from C++ ABI mismatch problems.
So what you would do is start from gtkmm source, and the normal Gtk libs that Fink has, and build gtkmm statically. ./configure --disable-shared --enable-static not only builds the libxxx.a files, but also configs the libtool .la files in the lib directory.
bob
On 7/1/06, jiho <jo.irisson@...400...> wrote:
[...snip...] gtk+2 and gtkmm2.4 are at version 2.6.4 in Fink unstable. I was wondering about the schedule of the integration of version 2.8 in Fink (given that 2.10 should be out shortly). [...snip...]
To be honest, I think mostly people are afraid to touch it. :)
I think what it will need is a concerted effort to hack up all of the gtk-using packages to be updated (in the manner we did to move to the 10.4 tree) and get everything moved at once.
so it seems i nothing will happen in the near future :-)