INSTALLCHECK(1)

πŸ’… INSTALLCHECK(1) β€” the libsolv girlie's guide to "wait, can I actually install this??"

okay bestie, so you know that feeling when you're about to install a package and the dependency gods are like "no ❀️"? yeah. that's what installcheck is here to save you from. it lives in the libsolv universe and it's lowkey one of the most useful little tools ever. no cap.


✨ NAME ✨

installcheck β€” find out which packages cannot be installed 🫢

like literally, it tells you which ones are giving "broken dependency" energy before you find out the hard way. iconic behaviour tbh.


🌸 SYNOPSIS 🌸

installcheck ARCH REPO1 REPO2... --nocheck NREPO1 NREPO2...

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: installcheck checks if all the packages in REPO1...REPON are installable. and a package counts as installable if there's a set of packages from the repositories that satisfies its dependencies. that's the whole definition. that's the bar. slay.

then there's the plot twist: the repositories that come after the --nocheck option are only used for dependency resolving β€” the tool does not check whether the packages inside those ones are installable. so they're like the backup dancers πŸ’ƒ, they show up and help the main act, but nobody's grading them.

heads up bestie: a Repository can be a solv file, a rpmmd primary.xml.gz file, a SUSE packages or packages.gz file, or a Debian Packages or Packages.gz file. so many flavours, all valid, we love a versatile queen. πŸŽ€

πŸ‘‘ AUTHOR πŸ‘‘

Michael Schroeder <mls@suse.de> β€” the actual legend behind this whole thing. thank you for your service fr fr πŸ’–


and that's the tea πŸ“ β€” brought to you by libsolv, dated 09/14/2018, page INSTALLCHECK(1). go check those packages, bestie, and may all your dependencies resolve on the first try. periodt. πŸ’…βœ¨