From: Olaf W. <wei...@ip...> - 2011-11-14 21:40:10
|
On 2011-11-14 11:28, g....@fr... wrote: > When working adding test suite on all perl packages, I understood we include twice sqlite code, once as sqlite package, once as DBD-SQLite as the second include his own version (3.7.8.6) of the code. > With a sed 's/if ( 0 ) /if ( 1 ) /' Makefile.PL, GDB-SQLite compile against system sqlite lib (would need to install sqlite before GBD-SQLite). Compilation is ok but that time, the package test suite badly fail. > Fedora and Debian compile against system lib and do nothing special to run the tests. > I haven't find what is wrong in our case, if it is related to our way to compile perl or something else. > > Another point of view is that we could not include sqlite package, let GDB-SQLite include the code and wrap the command to create a database in a perl script. OK, that would be a good simplification. IIRC there really is only 1 place where we use sqlite directly. Probably better to wait till next week though, after the 2.0.2 update. > There is too a perl DBI-Shell package that give access to a shell using DBI=>DBD-SQLite stack. Don't think we need to include that. Using DBD-SQLite should give us anything we need. > I could upgrade iw to 3.2 (with or without upgrading too libnl to 3.2.2). > libnl-3.2 add some configuration files and probably some overhead, compared to libnl-2.0 OK. > Another place I am working is the graphic stack, that will probably wait after 2.0.2 to be ready. > Reducing freetype size is not hard (commenting some modules we don't use). > > For libgd, I switched to debian 2.0.36 version that is used since lenny. > > Much harder is to understand what is exactly needed to be finally used on rrdtool. Actually rrdtool ask for pdf, svg support from cairo. That does not look very usefull for our use case. > The last point is that I really want to have a better cairo test suite as this is the only remaining package with so much errors. Yes, let's wait with those for next release (2.0.3 or 2.1.0). Olaf |