Linked by Eugenia Loli on Tue 29th Mar 2005 19:32 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



> >$ readelf -d /usr/bin/gimp | grep '(NEEDED)' | cut -d[ -f2 | cut -d] -f1
> How incredibly easy to figure this out. How user-friendly. NOT.
there is ldd to check binaries --- very easy to use:
<tt>ldd /usr/bin/gimp</tt>
and to find out, what package owns a file this binary depends on you ask pacman:
<tt>[damir@Asteraceae ~]$ pacman -Qo /lib/tls/libc.so.6<br/>
/lib/tls/libc.so.6 is owned by glibc 2.3.4-2 </tt>
... and namcap to check packages on dependencies --- also very easy to use against PKGBUILD's or pkg.tar.gz
... but the important thing is: for the packages in the repositories in most cases you don't need ABS and manipulation and don't need to care about dependences in detail! simply <tt>pacman -S whatever</tt> and start using it.