Hi, The modifications below were made to the graph-tool packages. I also renamed the package to conform to the debian guidelines, and I also made a package for python3. The package names are now python-graph-tool python3-graph-tool Cheers, Tiago On 01/05/2013 01:10 PM, Tiago de Paula Peixoto wrote:
On 01/05/2013 01:06 AM, Johannes Schauer wrote:
Hi,
I have some questions about the graph tool Debian package:
Why does it depend on libboost-all-dev? Out of all ~38k binary packages in Debian, only libfeel++-dev depends on libboost-all-dev. I dont see a reason for the graph-tool package to depend on libboost-all-dev. Why does it?
This is clearly an overkill... The idea behind it was that the inline() function of graph-tool allows for on-the-fly compilation of C++ code, and I usually would use different parts of the boost library. This is also why other -dev packages and g++ are listed as run-time dependencies.
The graph-tool binary package also depends on expat. Why? The expat package only ships the program /usr/bin/xmlwf which I dont see being used by graph-tool at all?
This is clearly an error. It should be libexpat1.
It also depends on python-dev. Why? Packages that are not *-dev packages should not need to depend on python-dev.
It also depends on the g++ package. The g++ package only ships the binary /usr/bin/g++ which, as far as I can see, is never executed by graph-tool?
This is because of the inline() functionality, as explained above.
I'm just asking because once I try to install the graph-tool package, apt-get tells me that it will fill 1036 MB of disk space with 323 new packages it needs to resolve graph-tool's dependencies. This seems somehow a bit like overkill to spend one gigabyte just to install graph-tool?
This is clearly excessive. I'll make the modifications such that only the bare minimum is required. If the user wants to use the inline() function, only then should the -dev packages be installed.
Thanks for pointing this out.
Cheers, Tiago
-- Tiago de Paula Peixoto <tiago@skewed.de>