opkg(1)

πŸ“¦ version 0.8.0, in nixos 26.05, nixpkgs unstable

πŸ‘‘ opkg(1) β€” the manual page but make it make sense πŸ’…

okay so bestie, you've found it: the opkg(1) manual. Yes, that's the User Commands one. Yes, I read the whole thing so you don't have to. Grab a πŸ“ and let's go.


✨ NAME ✨

opkg β€” a command line utility to install, upgrade and uninstall opkg software packages 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

opkg [OPTIONS...] sub-command [ARGUMENTS...]

πŸ’œ DESCRIPTION πŸ’œ

opkg is a simple little utility to install, upgrade and uninstall opkg software packages. It's a lightweight package management system, and it's based on Ipkg β€” like, that's its whole ancestry. Lowkey iconic lineage, no cap. πŸ‘‘


πŸŽ€ OPTIONS AND COMMANDS πŸŽ€

🌈 SUB-COMMANDS : PACKAGE MANIPULATION 🌈

This is the section where we actually do stuff. Main character energy only. ✨

  • update β€” Update list of available packages
  • upgrade β€” Upgrade installed packages
  • dist-upgrade β€” Upgrade operation that allows package removal. Heads up: only available on the libsolv backend πŸ‘€
  • install <package(s)> β€” Install package(s)
  • configure <package(s)> β€” Configure unpacked package(s)
  • remove <packages|glob> β€” Remove package(s). The glob works like a shell globbing pattern and could be something like 'pkgname*', '*file*' or similar 🫢
  • clean β€” Clean internal cache
  • flag <flag> <packages> β€” Flag package(s). Available flags (one per invocation):
    • hold
    • noprune
    • user
    • ok
    • installed
    • unpacked
  • version β€” Print version

🧚 INFORMATIONAL SUB-COMMANDS 🧚

Not me being obsessed with a read-only section. This is the "just tell me things" era and honestly? It ate. πŸ’–

  • list β€” List available packages
  • list-installed β€” List installed packages
  • list-upgradable β€” List installed and upgradable packages
  • list-changed-conffiles β€” List package configuration files which have been modified after installation
  • files <package> β€” List files belonging to package
  • search <file|glob> β€” List package providing file
  • find <regexp> β€” List packages with names or description matching regexp
  • info [package|glob] β€” Display all info for selected packages
  • status [package|glob] β€” Display all statuses for selected packages
  • download <package> β€” Download package to current directory
  • compare-versions <version1> <operator> <version2> β€” compare versions using following operators:
    • << β€” less than
    • < β€” less than or equal to
    • <= β€” less than or equal to
    • = β€” equal to
    • >= β€” greater than or equal to
    • > β€” greater than or equal to
    • >> β€” greater than
okay bestie I'm just the messenger πŸ™ˆ β€” that's exactly how the page lists the operators, duplicates and all. Don't come for me, come for the docs.
  • print-architecture β€” List installable package architectures
  • depends [-A] <package(s)|glob>
  • whatdepends [-A] <package(s)|glob>
  • whatdependsrec [-A] <package(s)|glob>
  • whatrecommends [-A] <package(s)|glob>
  • whatsuggests [-A] <package(s)|glob>
  • whatprovides [-A] <package(s)|glob>
  • whatconflicts [-A] <package(s)|glob>
  • whatreplaces [-A] <package(s)|glob>
  • verify <package(s)|glob> β€” Verifies the integrity of <pkg>, or all packages if omitted, by comparing the md5sum of each file with the information stored on the opkg metadata database. Detective mode fr fr πŸ”

⭐ OPTIONS ⭐

The flags. The seasoning. The little guys that change everything. πŸŽ€

  • -A β€” Query all packages not just those installed
  • -V <level>, --verbosity <level> β€” Set verbosity level to level. Verbosity levels:
    • 0 β€” errors only
    • 1 β€” normal messages (default)
    • 2 β€” informative messages
    • 3 β€” debug
    • 4 β€” debug level 2
  • -f <conf_file>, --conf <conf_file> β€” Use conf_file as the opkg configuration file
  • --cache-dir <directory> β€” Use a package cache
  • -t <directory>, --tmp-dir <directory> β€” Specify directory as temporary directory
  • -l <directory>, --lists-dir <directory> β€” Specify directory as package lists directory
  • -d <dest_name>, --dest <dest_name> β€” Use dest_name as the the root directory for package installation, removal, upgrading. dest_name should be a defined dest name from the configuration file, (but can also be a directory name in a pinch). iykyk πŸ’…
  • -o <directory>, --offline-root <directory> β€” Use directory as the root directory for offline installation of packages.
  • --add-dest <name>:<path> β€” Register path as installation target name for use in conjunction with --dest
  • --add-arch <arch>:<prio> β€” Register the package architecture arch with the numeric priority prio. Lower priorities take precedence.
  • --add-exclude <name> β€” Register package to be excluded from install
  • --add-ignore-recommends <name> β€” Register package to be ignored as a recomendee
  • --prefer-arch-to-version β€” Use the architecture priority package rather than the higher version one if more than one candidate is found.
  • --combine β€” Combine upgrade and install operations, this may be needed to resolve dependency issues. Only available for the internal solver backend.
  • --fields <field1>,<field2> β€” Limit display information to the specified fields plus the package name. Valid for info and status.
  • --short-description β€” Display only the first line of the description.
  • --size β€” Print package size when listing available packages

πŸ”₯ FORCE OPTIONS πŸ”₯

⚠️ real talk bestie: these override the checks that exist for a reason. They're not toys. Use them when you genuinely mean it, and know what you're asking for. 😭
  • --force-depends β€” Install/remove despite failed dependencies
  • --force-maintainer β€” Overwrite preexisting config files
  • --force-reinstall β€” Reinstall package(s)
  • --force-overwrite β€” Overwrite files from other package(s)
  • --force-downgrade β€” Allow opkg to downgrade packages
  • --force-space β€” Disable free space checks
  • --force-postinstall β€” Execute package postinstall scripts in offline installation mode
  • --force-remove β€” Remove package even if prerm script fails
  • --force-checksum β€” Don't fail on checksum mismatches
  • --noaction β€” No action - test only
  • --download-only β€” No action - download only
  • --nodeps β€” Do not follow dependencies
  • --install-recommends β€” Install any recommended packages. This flag overrides the no_install_recommends configuration option.
  • --no-install-recommends β€” Do not install any recommended packages
  • --force-removal-of-dependent-packages β€” Remove package and all dependencies
  • --autoremove β€” Remove packages that were installed automatically to satisfy dependencies
  • --host-cache-dir β€” Don't place cache in offline root dir
  • --volatile-cache β€” Use volatile cache. Volatile cache will be cleared on exit

πŸ’€ REPORTING BUGS πŸ’€

Found a bug? Say it with your chest, bestie β€” report it here:

https://bugzilla.yoctoproject.org/buglist.cgi?product=opkg

Copyright Β© Opkg development team.

Copyright Β© Ipkg development team.


🫢 and that's the whole page! This was opkg version 0.8.0, dated January 2025, brought to you by the opkg(1) girlies. Go forth and manage your packages, queen. Periodt. πŸ‘‘βœ¨

πŸ“¦ where this page comes from