3 | | * Extend packagefs to provide symlinks for base paths of packages and their dependencies (needed for dealing with packages that hard-code absolute paths). |
| 3 | * packagefs: |
| 4 | - Prepare for use in a chroot environment. Currently it resolves the package directory path in the kernel I/O context. |
| 5 | - Support packages being copied to the `packages` directory. Currently only moving works. |
| 6 | - Solve node removal issues. A currently executing program should not crash and burn when its package is removed. |
| 7 | - Provide information about active packages to the tools that need it (e.g. the package solver). |
| 8 | - Implement query support. |
| 9 | - If necessary, add a caching mechanism to speed up mounting it. |
9 | | * Work on tools to build Haiku packages in a clean chroot environment. |
10 | | |
11 | | * Define packaging guidelines and create a tool to check packages those. |
12 | | |
13 | | * Adjust build "recipes" for HaikuPorts packages as needed and build the packages. |
14 | | |
15 | | * Extend packagefs to provide information about active packages to the tools that need it (e.g. the package solver). |
16 | | |
17 | | * Implement the package solver (as Oliver proposed based on libsatsolver). |
18 | | |
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 | | |
21 | | * Implement query support in packagefs. |
22 | | |
23 | | * If necessary, add a caching mechanism to packagefs to speed up mounting it. |
24 | | |
25 | | * Implement a GUI package manager. |
26 | | |
27 | | * Make the `update` feature of the build system usable again. Currently for anything in the `haiku.hpkg` package the whole package has to be rebuilt, which takes a rather long time. |
| 20 | * Package kit/manager: |
| 21 | - Implement the package solver (as Oliver proposed based on libsatsolver). |
| 22 | - 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. |
| 23 | - Implement a GUI package manager. |