Npkg

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (Features)
m (wish added)
 
Line 42: Line 42:
 
# 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.
 
# 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=
 
=API=

Latest revision as of 08: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:

  1. Install
  2. Remove
  3. Upgrade
  4. Update
  5. Handle configuration files changes
  6. Run without stopping and asking questions, like overwriting config files (save new config as <pkg.conf>.new resp. <pkg.conf>.old)
  7. Ignore dependencies
  8. Restrict certain packages upgrades
  9. Check if a new version of itself exists before installing other packages.
  10. List all/installed/upgradeable packages
  11. search for a package by name/description
  12. download only
  13. probe all info about a package
  14. be able to set different config file
  15. be able to set different root dir
  16. be able to force downgrade
  17. be able to tell whether to cache or not to cache packages
  18. be able to do a "dry run"
  19. ignore restrictions (like deps/conflicts and such)
  20. progress indication!
  21. multi repos?
  22. install from repo/url/local
  23. when upgrading, confirm the list of pkgs to be upgraded before actually doing the upgrade.
  24. 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:

  1. sqlite3
  2. 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)

  1. tasn - programmer - #openmoko-cdevel@freenode
Personal tools

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

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)

Features

This list includes all the actions it should be able to do (even trivial ones)

Should be able to:

  1. Install
  2. Remove
  3. Upgrade
  4. Update
  5. Handle configuration files changes
  6. Run without stopping and asking questions, like overwriting config files (save new config as <pkg.conf>.new resp. <pkg.conf>.old)
  7. Ignore dependencies
  8. Restrict certain packages upgrades
  9. Check if a new version of itself exists before installing other packages.
  10. List all/installed/upgradeable packages
  11. search for a package by name/description
  12. download only
  13. probe all info about a package
  14. be able to set different config file
  15. be able to set different root dir
  16. be able to force downgrade
  17. be able to tell whether to cache or not to cache packages
  18. be able to do a "dry run"
  19. ignore restrictions (like deps/conflicts and such)
  20. progress indication!
  21. multi repos?
  22. install from repo/url/local
  23. when upgrading, confirm the list of pkgs to be upgraded before actually doing the upgrade.
  24. 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

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:

  1. sqlite3
  2. libcurl

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)

  1. tasn - programmer - #openmoko-cdevel@freenode