Variant of https://agill.net/pkgcmds for bitbake recipe/package investigation

[Notgnoshi]

• pkgdata files and directory hierarchy
• oe-pkgdata-util
• recipe name vs pkg name vs internal vs published package name

FAQ style + exposition around pkgdata and nomenclature

[Notgnoshi]

pkgdata directories:

• machine/<recipe> - a pkgdata file for each recipe. a PACKAGES: variable lists all the packages provided by the recipe.
• machine/runtime/<pkg> - a pkgdata file for the internal name for each package (e.g., glibc)
  • PN, PV, PR, PKG, RDEPENDS, RRECOMMENDS, FILES, PKGSIZE, etc
• machine/runtime-reverse/<pkg> - symlinks into ../runtime/ using the published name of each packages (e.g., libc6)
• machine/runtime-rprovides/<provides> - lists the set of packages that provide <provides>
• machine/extended/<pkg>.json.zstd - compressed pkgdata info - this is the source of truth for oe-pkgdata-util

[Notgnoshi]

FAQ

• What does package X depend on?
• What packages depend on X?
• What recipe provides package X?
• What layer defines recipe X?
• I have multiple recipes for a package, which one is used?
• What package ships <path>?
• How large is package X?