On 28 Mar 2005, at 04:36, Jeremy Higgs wrote:
The next package is gnome-python (2.4.2), which, because it depends on GNOME, has a mass of dependencies. I've been trying to make some sense out of them, but haven't figured out what dependencies should be included, and what versions. Are there any sort of guidelines for what dependencies should be included for a package relying on GNOME (or any part thereof)?
For runtime deps, I use the following:
/sw/var/logs# cat ~/bin/otool_deps
#!/sw/bin/bash
# "otool_deps pkgs" yields a comma separated list (possibly empty) (followed by a \n) of the packages
# on which the given (installed) pkgs depend according to otool _ excluding the given pkgs themselves.
dpkg -L $@ | xargs file | grep 'Mach\-O' | cut -f 1 -d ':' | xargs -r otool -L 2>/dev/null | grep -v ':$' \
| sed -r 's|^[[:space:]]*||g' | cut -f1 -d' ' | sort -u | xargs -r dpkg -S 2>/dev/null | cut -f1 -d':' \
| sort -u | grep -vxF "`tr ' ' '\n'<<<$*`" | xargs | sed 's| |, |g'
The output has then still to be completed by the dependencies of all scripts, python-stuff in your case, etc.
(Is there nothing available that would list all commands a given _ shell-, or perl- _ script
can possibly be called to execute ? )
For BuildDepends, a frequent bet is that a priori one can safely add any -dev pkg whose shlibs are runtime deps.
I is also useful to look at at your log-file to know what commands are executed, and what the configure script tests.
Then, in the info files of those pkgs, look for comments like "Any pkg that BuildDepends on this one must also.."
JF
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
