On 9-Nov-05, at 23:19 , Sebastien Maret wrote:
David Bacher <[EMAIL PROTECTED]> writes:
In pseudocode:
* Build and install your package to an isolated location
* find | file | grep to create a list of all binary objects
* otool -L each binary | grep /sw
* for each dependency in /sw, look up its package
I vaguely recall a long time ago seeing a script that would anayze
dpkg
contents (running otool on binaries in /sw/*bin/ and /sw/lib/ -- but
maybe I just thought it would be cool to write such a thing. :)
I have a script that does that in my experimental branch
(experimental/bmaret/finkdep). It uses otool to find the libraries on
which depends the program or the library, and search for the packages
that provides these libraries by looking at the .list files in
%s/var/lib/dpkg/info/. It outputs the Depends and BuildDepends in Info
format.
Thanks for this script. It looks like it will be very useful. I
believe that eventually this functionality should be built in to fink
validate. For now, your script should be mentioned in the packaging
documentation, in my opinion.
Kevin Horton
Ottawa, Canada
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
