Custom package manager

Refractor · 03-18-2013, 06:40 PM

Greetings!
Perhaps this is something for the programming section, but since I'm targeting LFS I thought first it'd be better to ask here.
I am writing a custom package manager to use with LFS and I was wondering if `ldd' is something I can count for auto-resolving dependencies, like for instance running

Code:

ldd $libs | awk '{print $3}'

for every executable/shared library that a package produces and then searching for the dependencies in a list of files, that belong to packages.
Something like

Code:

$ ldd bsdcpio | awk '{print $3}'
/tools/lib64/liblzma.so.5 -> xz-5.0.4
/tools/lib64/libpthread.so.0 -> glibc-2.17
/tools/lib64/libc.so.6 -> glibc-2.17
/tools/lib64/libgcc_s.so.1 -> gcc-4.7.2

Thanks.

kbp · 03-18-2013, 07:11 PM

Ldd would only determine your runtime shared object dependencies, applications are not necessarily that simple and will quite often call external programs to perform work on their behalf. Maybe you could investigate the configure script output/return code to determine what dependencies are required, but even then not all applications have a configure script either.

Refractor · 03-19-2013, 01:14 AM

It seems that `ldd' prints out all dependencies (even the dependencies of the dependencies) which is not what I need. I'll use `readelf -d' to fetch the runtime deps and will try to figure something for finding needed external applications. Thanks for pointing that out.