Actually, remy just applied a patch to fix pyalpm compilation, and you can use this PKGBUILD to get it working with pacman-git: https://github.com/neersighted/PKGBUILDs/blob/master/pyalpm-pacman41-git/PKG... On Sat, Mar 2, 2013, at 03:01 PM, Dave Reisner wrote:
On Sat, Mar 02, 2013 at 11:50:57PM +0100, Johannes Löthberg wrote:
On 02/03/2013 23:46, Dave Reisner wrote:
On Sat, Mar 02, 2013 at 11:35:40PM +0100, oliver wrote:
Hello,
is there an easy way to find out, which package dependencies a package has?
Say, i want to write the PKGBUILD for a package, and the compilation on my system (.7configure/cmake and make) does work without problems.
Then I don't get a message about missing libraries. So, it's easy to compile the stuff, but needs some effort to find out the dependencies.
Possibly with ldd the linked stuff can be found out, but the library names not necessarily are the same as the names of the package that provide these libraries.
So, it may need some effort to find out the packages.
Is there an easy way to find out the package names?
Maybe someone already has written a script that reverse-lookups the package names from ldd-output?
Any ideas on that?
Ciao, Oliver
This is probably what you're looking for:
https://github.com/falconindy/bin-scripts/blob/master/elf2pkgs
You can get a concise list by running this over the pkg/ directory after building:
find pkg/ -type f -executable -exec elf2pkgs {} + 2>/dev/null
d
Wouldn't it be easier to just use namcap, or am I missing something?
Probably. I run pacman from git, so namcap doesn't work for me.
-- Neer Sighted, Hacker http://neersighted.com | neersighted@myopera.com {01DC2056}