These are the TODO items for the Haiku '''Package Management'''.

=== packagefs ===
  * Prepare for use in a chroot environment. Currently it resolves the package directory path in the kernel I/O context. This is only a problem for packagefs mounted after chroot (low priority).
  * Support packages being copied to the `packages` directory. Currently only moving works.
  * Provide information about active packages to the tools that need it (e.g. the package solver).
  * If necessary, add a caching mechanism to speed up mounting it.

=== Build system ===
  * Before creating packages (e.g. the user guide), all files must be identified, since packagefs is read-only.

=== Package building ===
  * Work on tools to build Haiku packages in a clean chroot environment.
    * Status: There's a package management [http://ports.haiku-files.org/browser//haikuporter/branches/package-management branch of haikuporter] which builds HPKGs. It doesn't do chroot building yet (requires pkgman to solve dependencies and install packages) and probably should use another recipe format (e.g. RPM .spec files).
  * Define packaging guidelines and create a tool to check packages those.
  * Adjust build "recipes" for HaikuPorts packages as needed and build the packages.
    * Status: There's a package management [http://ports.haiku-files.org/browser//haikuports/branches/package-management branch of haikuports] with recipes for several packages already updated for building HPKGs.

=== Package kit/manager ===
  * Implement the package solver (as Oliver proposed based on libsolv).
    * Status: There's a [https://github.com/weinhold/libsolv WIP port] of libsolv. It's more or less complete, but mostly untested (a reasonable amount of packages are needed to test it). The Haiku solver API is missing yet.
  * Extend the package kit and the (CLI) package manager to support adding, removing, and updating packages. That probably also involves work on a server-side (i.e. repository) part.
  * Implement a GUI package manager.

=== Miscellaneous ===
  * Modify Expander to use a directory instead of the `expander.rules` file. This way a package (like xz-utils or p7zip) can contribute a single file with the rules for its tools.
    * Ticket: #8494