| 1 | | = Package Management TODO = |
| 2 | | |
| 3 | | * packagefs: |
| 4 | | - 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. |
| 5 | | - Support packages being copied to the `packages` directory. Currently only moving works. |
| 6 | | - Provide information about active packages to the tools that need it (e.g. the package solver). |
| 7 | | - If necessary, add a caching mechanism to speed up mounting it. |
| 8 | | |
| 9 | | * Build system: |
| 10 | | - Before creating packages (e.g. the user guide), all files must be identified, since packagefs is read-only. |
| 11 | | |
| 12 | | * Package building: |
| 13 | | - Work on tools to build Haiku packages in a clean chroot environment. |
| 14 | | - Define packaging guidelines and create a tool to check packages those. |
| 15 | | - Adjust build "recipes" for HaikuPorts packages as needed and build the packages. |
| 16 | | |
| 17 | | * Package kit/manager: |
| 18 | | - Implement the package solver (as Oliver proposed based on libsatsolver). |
| 19 | | - 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. |
| 20 | | - Implement a GUI package manager. |
| 21 | | |
| 22 | | * Miscellaneous: |
| 23 | | - [[ticket:8494]]: 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. |
