RPMDEPS(1)
π RPMDEPS(1) π
okay bestie, so this is a page from the General Commands Manual and it's all about a lil tool called rpmdeps π yes the name is giving "rpm + deps", you ate that guess, gold star β
β¨ NAME β¨
rpmdeps β generate RPM package dependencies π¦
πΈ SYNOPSIS πΈ
rpmdeps <operation> [options]
rpmdeps <operation> [options] FILE ...
π DESCRIPTION π
so like, rpmdeps generates package dependencies for one or more files. where do the files come from? two options, bestie: either a list of filenames on the standard input, or straight up command line arguments. your choice, your vibe π«Ά
okay important tea tho β rpmdeps is not normally invoked directly. like, that's not the moment. BUT. doing it anyway is genuinely useful for troubleshooting dependency generation and for developing brand new dependency generators π so it's giving "don't talk to me, I'm debugging."
btw you can find out where rpmdeps lives with:
rpm -E "%{_rpmconfigdir}"
and one more thing, no cap: the actual rpmdeps command is only used for automatic dependency generation in a legacy compatibility mode of rpmbuild(1). periodt.
π§ OPERATIONS π§
pick your fighter, bestie β these are all the operations:
--alldepsβ print all the dependencies. everything. the whole plate π--conflictsβ print the conflicts dependencies.--enhancesβ print the enhances dependencies.--obsoletesβ print the obsoletes dependencies.--orderwithrequiresβ print the orderwithrequires dependencies.-P,--providesβ print the provides dependencies.--recommendsβ print the recommends dependencies.-R,--requiresβ print the requires dependencies.--suggestsβ print the suggests dependencies.--supplementsβ print the supplements dependencies.
π ARGUMENTS π
FILEβ any regular file. that's it. any. regular. file. simple as π
π OPTIONS π
for the options that are common to all operations, go peek at rpm-common(8) β they live over there, not here, and we respect the split π
π₯ ENVIRONMENT π₯
RPM_BUILD_ROOTβ the prefix path to strip out when generating dependencies based on actual paths. so like, it's the "okay ignore this part of the path" setting β¨
π EXIT STATUS π
on success? 0 is returned. anything else? a nonzero failure code otherwise. classic. iconic. predictable. π
π EXAMPLES π
okay now the fun part, here's how you actually use it:
rpmdeps --requires /bin/lsβ outputs the automatic requires dependencies of thels(1)binary. yes,ls. the little guy. and now you know what it needs πfind popt-1.19-build/BUILDROOT -type f | /usr/lib/rpm/rpmdeps -Pβ outputs the automatic provides of all files in thepopt-1.19-build/BUILDROOTdirectory. pipe it, princess π
π¦ SEE ALSO π¦
rpm(8), rpmbuild(1), rpm-common(8)
and that's the whole page, bestie β you understood it, you're literally the main character of dependency generation now ππ
this was RPM 6.1.0, dated 2026-08-20 β mwah, sending you a kiss on the forehead, go generate some deps πβ¨
π¦ where this page comes from
- ubuntu stonking: rpm 6.1.0-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms