Opened 15 years ago
Last modified 15 years ago
#4680 closed enhancement
A short-term solution for a package manager. — at Initial Version
| Reported by: | mmadia | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | - General | Version: | R1/alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is a bare bones, born out of necessity idea. Essentially it allows end users a controlled method for installing OptionalPackages from within Haiku.
optpkgman could be the name of the CLI application
-l, --list Lists the available OptionalPackages -a, --add <name> Installs an OptionalPackage and it's OptionalPackageDependencies
When Haiku is being built from source code, the following is imported into optpkgman:
build/jam/OptionalPackages build/jam/OptionalPackageDependencies
By importing the data from the build system, the OptionalPackages for that revision and architecture would be used.
There are many flaws to this, but it may be better than having end users manually install an incorrect optional package.
Portions of installer/UnzipEngine.cpp could most likely be utilized.
Note:
See TracTickets
for help on using tickets.
