= Package Management TODO =

 * 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 mount after chroot.
   - Support packages being copied to the `packages` directory. Currently only moving works.
   - Solve node removal issues. A currently executing program should not crash and burn when its package is removed.
   - Provide information about active packages to the tools that need it (e.g. the package solver).
   - Implement query support.
   - 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.
   - Define packaging guidelines and create a tool to check packages those.
   - Adjust build "recipes" for HaikuPorts packages as needed and build the packages.

 * Package kit/manager:
   - Implement the package solver (as Oliver proposed based on libsatsolver).
   - 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:
   - Revise the use of `gBootDevice` in the kernel modules code. The checks probably need to be adjusted, since a mounted boot volume doesn't mean that the modules can be read from the FS yet. This is only possible after the system packagefs has been mounted.
   - 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.