Npkg
From Openmoko
Tomhacohen (Talk | contribs) |
m (wish added) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | This package manager was created to replace opkg in low memory environments. (openmoko/slugos/more?) | + | This package manager was created to replace [[opkg]] in low memory environments. (openmoko/slugos/more?) |
It will hopefully be both memory efficient and fast, though the emphasis is on memory efficiency, since we have unlimited time though not unlimited memory. | It will hopefully be both memory efficient and fast, though the emphasis is on memory efficiency, since we have unlimited time though not unlimited memory. | ||
| Line 24: | Line 24: | ||
# Update | # Update | ||
# Handle configuration files changes | # Handle configuration files changes | ||
| + | # Run without stopping and asking questions, like overwriting config files (save new config as <pkg.conf>.new resp. <pkg.conf>.old) | ||
# Ignore dependencies | # Ignore dependencies | ||
# Restrict certain packages upgrades | # Restrict certain packages upgrades | ||
| Line 40: | Line 41: | ||
# multi repos? | # multi repos? | ||
# install from repo/url/local | # install from repo/url/local | ||
| + | # when upgrading, confirm the list of pkgs to be upgraded before actually doing the upgrade. | ||
| + | # Enable removing of Packages (dependencies) which aren't needed anymore (depclean) | ||
| + | |||
| + | =API= | ||
| + | The basic design is a library, this section lists the needed api. | ||
=Design choices= | =Design choices= | ||
| Line 57: | Line 63: | ||
# tasn - programmer - #openmoko-cdevel@freenode | # tasn - programmer - #openmoko-cdevel@freenode | ||
| + | |||
| + | [[Category:Package management]] | ||
Latest revision as of 09:31, 29 July 2009
This package manager was created to replace opkg in low memory environments. (openmoko/slugos/more?)
It will hopefully be both memory efficient and fast, though the emphasis is on memory efficiency, since we have unlimited time though not unlimited memory.
It is not yet in development, it's in the characterization stage. Please feel free to help, as this is the most important part.
Please read the introduction section source code: git://github.com/tasn/npkg.git
Contents |
[edit] Introduction
npkg (Nano pkg) conforms to the following coding convention: Coding Conventions Please read and follow.
Please help and add ideas to the projects wiki pages. (for instance the features page)
[edit] Features
This list includes all the actions it should be able to do (even trivial ones)
Should be able to:
- Install
- Remove
- Upgrade
- Update
- Handle configuration files changes
- Run without stopping and asking questions, like overwriting config files (save new config as <pkg.conf>.new resp. <pkg.conf>.old)
- Ignore dependencies
- Restrict certain packages upgrades
- Check if a new version of itself exists before installing other packages.
- List all/installed/upgradeable packages
- search for a package by name/description
- download only
- probe all info about a package
- be able to set different config file
- be able to set different root dir
- be able to force downgrade
- be able to tell whether to cache or not to cache packages
- be able to do a "dry run"
- ignore restrictions (like deps/conflicts and such)
- progress indication!
- multi repos?
- install from repo/url/local
- when upgrading, confirm the list of pkgs to be upgraded before actually doing the upgrade.
- Enable removing of Packages (dependencies) which aren't needed anymore (depclean)
[edit] API
The basic design is a library, this section lists the needed api.
[edit] Design choices
It seems like using sqlite3 and libcurl are the best solutions for our purposes. I'm considering using glib as well for data structures, though about that I'm still not sure and would like someone to help me think about pros and cons.
It'll probably be written in C and maybe at first will use shell (bash?) scripts for help when needed. (although target is C only).
In conclusion:
Probable dependencies:
- sqlite3
- libcurl
[edit] Volunteers
Please add yourself to this list if you think you'd like to give us a hand (specify nick/name, area of expertise and a way to contact)
- tasn - programmer - #openmoko-cdevel@freenode
