Languages: |
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català |
Opkg is a lightweight package management system based on Ipkg.
Mid December, 2008, the project moved to Google code: http://code.google.com/p/opkg/
Prior to that date, a mailing list for discussion was available here: http://lists.openmoko.org/mailman/listinfo/opkg-devel Source code was available in the subversion repository: http://svn.openmoko.org/trunk/src/target/opkg/. The repository could also be viewed online.
You can learn how to create own Opkg packages on the Ipkg site.
Packages should install .desktops at the very end of the installation process. This ensures that the icons referenced in the .desktop file are available. Reference
This is a list of features that have been completed. Mostly this is a list of changes from Ipkg.
The following ipkg patches have been applied:
These are features either under development or planned for inclusion before the next release.
This is a list of possible issues or known bugs.
dd if=/dev/zero of=/media/card/file.swap bs=1M count=512
dd if=/dev/zero of=/media/card/file.swap
mkswap /media/card/file.swap
swapon /media/card/file.swap
opkg upgrade
swapoff or reboot
Next time you will simply need to reactivate the swap before upgrading.
It looks like, in some cases, Opkg will return an error code if something goes wrong. Here's a list that I pulled from the error.h file:
Configuration Errors:
killall packagekitd
Package Errors
Install Errors
NOTE: I had a problem where I was trying to manually install a package that had dependencies. The dependencies had a bad signature (actually, my signature files were bad). Instead of returning 17 because of the bad signature, it returned 14 because of a dependency problem. So if you get a 14, try installing that package by itself and see what you get. --Jtickle 18:16, 23 July 2008 (EST) |
Q. What version of Ipkg is Opkg based on?
A. It is based on the ipkg-0.99.163 tarball
Q. Why "fork" and rename Ipkg?
A. Ipkg is no longer actively maintained upstream and there are potential trademark issues with using the Ipkg name
Q. Does opkg have a feature similar to APT pinning?
A. Yes you can define priorities on the architecture field (the second field in a feed definition) in /etc/opkg/arch.conf
Q. Does opkg have an auto completion system ?
A. Yes, it's a contribution script available at the upme blog
Q. How similar is the ipk format, to the deb format? They look very similar; the data and control tar balls are identical as far as i can tell.
A. Very similar. ipk files are basically deb files with documentation removed, and ipkg is even supposedly able to handle deb files. Opkg can install .deb packages directly, with no change. There may be issues with some packages, concerning preinst and postinst scripts
At one point I ended up doing a complete upgrade before i had updated my opkg. As a result i borked a lot af packages. To reinstall them all, you can use this little sed magic.
opkg -force-reinstall install `opkg list_installed | sed 's/ - .*//'
Languages: |
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català |