View source for Npkg

From Openmoko

← Npkg
Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Return to Npkg.

Retrieved from "http://wiki.openmoko.org/wiki/Npkg"
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. Ignore dependencies
  7. Restrict certain packages upgrades
  8. Check if a new version of itself exists before installing other packages.
  9. List all/installed/upgradeable packages
  10. search for a package by name/description
  11. download only
  12. probe all info about a package
  13. be able to set different config file
  14. be able to set different root dir
  15. be able to force downgrade
  16. be able to tell whether to cache or not to cache packages
  17. be able to do a "dry run"
  18. ignore restrictions (like deps/conflicts and such)
  19. progress indication!
  20. multi repos?
  21. install from repo/url/local

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