Changes between Version 1 and Version 6 of Ticket #4680
- Timestamp:
- Nov 24, 2009, 4:12:30 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4680
- Property Owner changed from to
- Property Summary A short-term solution for a package manager. → [patch] Script for installing OptionalPackages from within a current installation
-
Ticket #4680 – Description
v1 v6 1 1 This is a bare bones, born out of necessity idea. Essentially it allows end users a controlled method for installing OptionalPackages from within Haiku. 2 2 3 `optpkgman` could bethe name of the CLI application3 `optpkgman` is the name of the CLI application 4 4 {{{ 5 -l, --list Lists the available OptionalPackages 6 -a, --add <name> Installs an OptionalPackage and it's OptionalPackageDependencies 5 Usage: ./optpkgman.sh [-l] [-a] 6 -l List installable packages 7 -a Add a package and all of it's dependencies 7 8 }}} 8 9 9 When Haiku is being built from source code, the following is imported into optpkgman: 10 {{{ 11 build/jam/OptionalPackages 12 build/jam/OptionalPackageDependencies 13 }}} 14 By importing the data from the build system, the OptionalPackages for that revision and architecture would be used. 10 There are many flaws to this method. But it may be better than having end users manually install an incorrect optional package, as the correct version and it's dependencies are installed and have any symlinks created. 15 11 16 There are many flaws to this, but it may be better than having end users manually install an incorrect optional package.17 12 18 Portions of [http://dev.haiku-os.org/browser/haiku/trunk/src/apps/installer/UnzipEngine.cpp src/apps/installer/UnzipEngine.cpp] or [http://dev.haiku-os.org/browser/haiku/trunk/build/scripts/build_haiku_image build/scripts/build_haiku_image] could most likely be utilized.13 The script will determine the revision of Haiku and use that to download the appropriate build/jam/.... files from svn.