Om 2008 Installer

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(moving content to Manuals/Om 2008)
(→‎Useage)
 
Line 15: Line 15:
 
|}
 
|}
  
−
== Useage ==
+
== Manual ==
  
 
see [[Manuals/Om 2008#Installer]]
 
see [[Manuals/Om 2008#Installer]]

Latest revision as of 23:19, 29 July 2009


Contents

[edit] Introduction

The Openmoko Installer (Codename: Assassin) is a tool for installing, updating and uninstalling programs on your Neo.

categories
choose program
install application
install application

[edit] Manual

see Manuals/Om 2008#Installer

[edit] Features

  • Installer is a specialized GUI front-end of Packagekit over DBus interface.
  • Installer should be run with stable network conditions and power supply. Once Installer is launched, it actively tries to connect to installed repositories. Timeout will make it unresponsive if the network condition is not stable. If you do not have access to WiFi, a USB connection is recommended.
  • Installer refreshes the package meta-data every 2 days.
  • The default Packagekit backend on Neo is opkg, but it is not restricted to opkg.
  • You can also talk with Packagekit through DBus.
  • Installer will launch packagekitd automatically, which will lock the libopkg to avoid synchronization trouble. Normally, the packagekitd terminates itself after about 5 minutes. If you want to use 'opkg', you may terminate Installer and: 
killall packagekitd

[edit] See also

[1] Installer project - http://code.google.com/p/om-assassin/

[2] Packagekit project - http://packagekit.org/

[3] Opkg package management - Opkg

[4] List of Users Repositories

Retrieved from "http://wiki.openmoko.org/index.php?title=Om_2008_Installer&oldid=73568"
Personal tools
Key pages on:
Om 2008


Introduction

The Openmoko Installer (Codename: Assassin) is a tool for installing, updating and uninstalling programs on your Neo.

categories
choose program
install application
install application

Useage

see Manuals/Om 2008#Installer

Features

  • Installer is a specialized GUI front-end of Packagekit over DBus interface.
  • Installer should be run with stable network conditions and power supply. Once Installer is launched, it actively tries to connect to installed repositories. Timeout will make it unresponsive if the network condition is not stable. If you do not have access to WiFi, a USB connection is recommended.
  • Installer refreshes the package meta-data every 2 days.
  • The default Packagekit backend on Neo is opkg, but it is not restricted to opkg.
  • You can also talk with Packagekit through DBus.
  • Installer will launch packagekitd automatically, which will lock the libopkg to avoid synchronization trouble. Normally, the packagekitd terminates itself after about 5 minutes. If you want to use 'opkg', you may terminate Installer and: 
killall packagekitd

See also

[1] Installer project - http://code.google.com/p/om-assassin/

[2] Packagekit project - http://packagekit.org/

[3] Opkg package management - Opkg

[4] List of Users Repositories