pkgsanitychecks(1)

πŸ’– pkgsanitychecks(1) β€” the vibe-check-your-package manual πŸ’–

okay bestie, so this is the manual page for pkgsanitychecks, straight out of the General Commands Manual section. It's a tiny little gremlin of a tool that looks at your binary packages and goes "hmm, that's not it" when something's built wrong. Let's get into it. ✨


🌸 NAME 🌸

pkgsanitychecks β€” run sanity checks on the package

yes it's literally just the vibe check but for packages. no cap.


πŸŽ€ SYNOPSIS πŸŽ€

pkgsanitychecks directory

one argument, one job, one girlboss. she takes a directory and she does her thing.


πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea: pkgsanitychecks runs sanity checks on the binary packages, and it will let the build fail if the sanity checks don't pass. Like, she's not here to be your friend about it β€” if the checks flop, the build flops. πŸ’€

The following checks are run:

  • Location of public python modules β€” Starting with python-2.6, the public python modules are expected to be placed in /usr/lib/pythonX.Y/dist-packages instead of /usr/lib/pythonX.Y/site-packages. ma'am, dist-packages is the address, site-packages is not it anymore.
  • Files in /usr/local β€” Checks if any files are placed in /usr/local instead of /usr. we do not do /usr/local around here, we do /usr, periodt.
  • Files in /usr/share/initramfs-tools/hooks/ β€” Checks if any files placed in /usr/share/initramfs-tools/hooks/ are not executable. those hooks gotta be executable, bestie, otherwise it's giving "decorative" and that's not the assignment. πŸ”₯

πŸ’… ENVIRONMENT VARIABLES πŸ’…

  • NO_PKG_MANGLE β€” If this variable is set to a nonempty value, then pkgsanitychecks is disabled. This is most useful if source packages build nested binary packages as part of their build. basically: nested builds get a hall pass, set this and she sits this one out. 🫢
🌈 heads up: set it to a nonempty value. Empty string means she's still clocked in and ready to judge.

πŸ‘‘ AUTHOR πŸ‘‘

pkgsanitychecks is developed by Matthias Klose <doko@ubuntu.com>. shoutout to the developer, main character energy fr fr πŸ’–


and that's the whole manual, bestie β€” short, sweet, and fully committed to making your build behave. πŸ¦‹βœ¨

This page is from the General Commands Manual, authored by Matthias Klose, dated January 05, 2009. iykyk β€” oldie but a goodie, and yes the copyright-and-date energy stays on the record. πŸŽ€β­