Npkg

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(added link to git repo)
(added volunteers section)
Line 19: Line 19:
  
 
Should be able to:
 
Should be able to:
  # Install
+
# Install
  # Remove
+
# Remove
  # Upgrade
+
# Upgrade
  # Update
+
# Update
  # Handle configuration files changes
+
# Handle configuration files changes
  # Ignore dependencies
+
# Ignore dependencies
  # Restrict certain packages upgrades
+
# Restrict certain packages upgrades
  # Check if a new version of itself exists before installing other packages.
+
# Check if a new version of itself exists before installing other packages.
  # List all/installed/upgradeable packages
+
# List all/installed/upgradeable packages
  # search for a package by name/description
+
# search for a package by name/description
  # download only
+
# download only
  # probe all info about a package
+
# probe all info about a package
  # be able to set different config file
+
# be able to set different config file
  # be able to set different root dir
+
# be able to set different root dir
  # be able to force downgrade
+
# be able to force downgrade
  # be able to tell whether to cache or not to cache packages
+
# be able to tell whether to cache or not to cache packages
  # be able to do a "dry run"
+
# be able to do a "dry run"
  # ignore restrictions (like deps/conflicts and such)
+
# ignore restrictions (like deps/conflicts and such)
  # progress indication!
+
# progress indication!
  
 
=Design choices=
 
=Design choices=
Line 46: Line 46:
  
 
Probable dependencies:
 
Probable dependencies:
  # sqlite3
+
# sqlite3
  # libcurl
+
# 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)
 +
 
 +
# tasn - programmer - #openmoko-cdevel@freenode

Revision as of 22:05, 25 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

Contents

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!

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.

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
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

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:

 # Install
 # Remove
 # Upgrade
 # Update
 # Handle configuration files changes
 # 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!

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.

In conclusion:

Probable dependencies:

 # sqlite3
 # libcurl