Script to get/set dependencies/required packages in a slackbuild
 

To get the dependencies of my packages, i used to use "requiredbuilder", but
it does not exactly what i want to. So, i wrote my own "get_deps.sh" which does the
following:

• detect only hard dependencies(using "readelf -d", not "ldd") in all libs/binaries in the current package
• check if the current package itself already covers some needed libs( e.g. ffmpeg does), and so don't list the package itself
• prefer listing *solibs*txz if dependencies are found in multiple packages
• avoid listing aaa_elflibs and cxxlibs, if dependencies are also covered in other packages
• Better performance than requiredbuilder

Usage: chmod 755 get_deps.sh, put it somewhere in $PATH, then execute it in a slackbuild right before makepkg:

The Script is attached as .txt, as i didn't found a way to upload it as .sh.

Feedback is welcome :-)

Nice :)

I was giving it a try since my own buildscripts have support for installed requiredbuilder and will create a slack-required if requested.

I don't know much about package managers and slack-required files, the code that is included in my buildscripts is mature and i do not use it myself anymore.

Two questions:
getdeps will produce a slack-required file like that:
while requiredbuilder gives a package each line:
and i can use the -v option to add version info to slack-required:
Is there a difference between comma-separated and "one dep each line" and can version information be added to the output?

I did another test for ffmpeg:
requiredbuider:
getdeps:
There are a few differences:
If i do a ldd libavcodec.so.56.60.100 i get a dependency to libXrandr which is not listed for getdeps. readelf -d does not list libXrandr. Not sure which dep-finder is correct here...

That package is already included in slackware packages i believe

Which package? This thread is about the getdeps script.

I have a smiliar script but that is not like getdeps, it just checks all packages installed for bin/lib-files and their dependencies. I'm using ldd but the OP said he is using readelf. So me is just interested in his script (and maybe a replacement of requiredbuilder which is not maintained anymore... AFAIK) and the differences between ldd and readelf -d.

@franzen : again, nice job :cool:
I just compared requiredbuilder with getdeps for ffmpeg:

requiredbuilder:
getdeps:
If kcalc is doing right this is about 90% faster :D i like that!

I use comma-separated deps in my slack-repo since years(generated with requiredbuilder -b -c -p -z ), client is slapt-get, maybe it works also with linebreaks

Version information can't be added. For me, this was never useful. I (almost)always have only one version of a package in my repo, and have to keep track that it fits together with the rest of the repo. In the rare cases i needed two version(lets say guile and guile1.8), the package has another name anyway. Versions might be be useful when mixing diffrent repos , but in that case, there might a lot of other things go wrong(in my opinion). In short, i don't need Version in the required string, they just make the dep-text longer.

Beside the possibililty that getdeps contain bugs ;-), different output is intentional, depending on the package. ldd lists "too much", it lists dependencies of dependecies.
ffmpeg actually has no dependency e.g. on db48, ffmpeg depends on a package that depends on db48. While this will for now work to install ffmpeg, it might not work if the repo is combinded with the next slackware-release, as dependencies might have changed/packages removed and so on. You might be forced to rebuild working software, not for a new version, but that the required-string is correct again.

i mean libXrandr is already included in Slackware

you can run sbbdep against the DESTDIR,
http://a4z.bitbucket.org/docs/sbbdep...e_query_option

in this way it's possible to include it in a build
I think it will be even faster, with the right options for sure
and more correct, since it checks also for some internals, eg just including a required lib in a package does not necessary mean it will be found, on the other hand also files can be found that are not in a linker path but somewhere else on the system.

whole documentation:
http://a4z.bitbucket.org/docs/sbbdep/

I am moving the doc from here to the new location , so if something missing, check here
https://bitbucket.org/a4z/sbbdep/wiki/Home

Some tools parse the .info file for dependencies from the SBo tree.

Mostly everything already in the main Slackware tree is generally not listed.

I wasn't aware that this tool exists, it seems much more powerful and may do all
that i wanted to get from my get_dep-script. Unfortunately, i can't build it
on slackware 14.1, i used the instructions from your slackbuilds-buildscript, make says:
Even faster is nice to have. My script does also search for everything in the current package what has to do with ELF, and therefore should find everything needed in /var/log/packages/.
In the installed packages, it only searches for deps which are in /etc/ld.so.conf, as the libs have to be located there to work with ldconfig and so on. If libs are somewhere in the package, this should be corrected when building a package, in my opinion.

Question to sbbdep: according to your docs, it will for my usecase output something like this:
If i understand it right from elf_libs.txt,
aaa_elflibs should be avoided to be a dependency-package where possible, as the containing libs will never get (security)updates until the next slackware-release. Therefore i remove the "or-pipes" and aaa_elflibs in my script, if the dependency is covered by another package. Do you agree with that, or is there another intention to add aaa_elflibs?

I worked with "cmake . -DCMAKE_INSTALL_PREFIX=/usr" for some reason.
Beside aaa_elflibs,cxxlibs and preferred solibs-packages, "sbbdep --quiet --short" seems to give me the same output as my script does.
Sbbdep is very fast, if one doesn't take in account the initial indexing. Does the index get updated, if there are new/updated packages in /var/log/packages/ ?
Sbbdep will help me with many tasks, thank you very much for creating such a great tool :cool:

For my usecase described in the first post, i think will stick to my script, as i wanted to replace the external dependency(requiredbuilder) from my build-tools by bash-code, and i
would have to "sed" the output of sbbdep to get what i want.

sbbdep is also available via slackbuilds.org, you can have a look at the build script in how to use the options(or not to set the CMAKE_CXX_FLAGS ;-)
http://slackbuilds.org/repository/14...?search=sbbdep

the index updates automatically, except if you disable it explicit via option of course.
so after install/remove/update its good to not disable it at least once
or run it without any options to just refresh the cache after install/remove/update.

if there is nothing to update, the internal check does not take to much time, on ssd it's nearly irrelevant, on hds it depends if files are in the cache or not if it is measurable.

I have to think about the aaa_elflibs, good that you mention this, thanks.
maybe Slackware should care about the aaa_elflibs since it can, and therefore IMHO shoud be updated, see this thread.
http://www.linuxquestions.org/questi...ge-4175537158/

not sure about the cxxlibs name, the salix dep files contain them, and as the aaa_elflibs, if you want a minimal installation you can use them.

and both packages might be a real alternative for a minimum install

I have to do some research for those packages, I already know that my personal opinion is that the distribution has to keep them actual, but my opinion might be for sure irrelevant.

do you want to file an issue?
https://bitbucket.org/a4z/sbbdep/issues

it's not a big deal to avoid these packages, or enable user filter in general what might be the better way

I wrote my own buildscript using CMAKE_CXX_FLAGS by adding "-std=c++11" and "-lpthread" ;)

My scripts do now support requiredbuilder and sbbdep. The missing feature in sbbdep from requiredbuilder using ADD or EXCLUDE to modify the slack-required file is a pitty but i added some code to emulate that missing feature. While i'm still interested in the get_deps.sh script it looks like this script does support that in the same way as requiredbuilder does.

Since no one was able to answer my question about the comma-separated list of dependencies i modified the get_deps.sh script, see attached patch.

I also added some code to add the version of the dependency, just use get_deps.sh --version.

Default output:
Using --version:
Patch:
I will have a deeper look into the get_deps.sh script... it really looks interesting and might be a good way to include creating slack-required files automatically to my own buildscripts if neither requiredbuilder nor sbbdep is installed.

Thanks, i'll have a closer look and will try to build the version-feature into, hopefully
avoiding additional "find"s for better performance.

The comma-separated list has no real technical difference to multiple rows, so far i know.
But if listet in an a PACKAGES.TXT in a repository, i think it disturbs if there are hundreds of extralines.

cxxlibs seem to be removed from -current, these libs seem to be added aaa_elflibs.
One of the ideas of aaa_elflibs is to avoid upgrade-issues, so old libraries will have
to there, also if newer versions gonna be added. It will grow if is has to contain "everything", which isn't very suitable for a minimal install i think.