View source for Installing alien package

From Openmoko

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 Installing alien package.

Personal tools


The problem is that some packages exist in both the fundamental distribution - and other repositories - with same names, but (newer) with other dependencies, other source code includes and other compilation options, which can and often will break the installation.

So e.g. do not use "opkg upgrade" when non-distribution (e.g. non-OM2009) repositories are included. It often breaks the installation.

Solution hack?

Please surround the non-distribution (alien) package install with:

  1. Addition of the required repository
  2. opkg update # Update database.
  3. Install the package(s)
  4. remove the non-distribution repository from opkg. E.g. "rm /etc/opkg/opkg-feed.conf"
  5.  ? Is this required?: opkg update # Update database with only the fundamental distribution packages?

Future package management system wish

Wish: Actually the package management system should cope with it. The fundamental distribution with a given version number/revision should have higher precedence, and other repositories should have lesser precedence. Maybe the best would be that the package had a distribution list in which it can be "fundamental".

Maybe the package management system should consult a check post (by name and some checksum), so an installer can be informed before installation of the package on the given fundamental distribution:

  • Not tested
  • Tested
    • Security:
      • Installation damage (permanent; system can not (re)boot,...)
      • Non-permanent damage (uninstall recovers the installation):
        • Only configuration
        • Data
      • Contains malware
      • Contains virus
      • Crashes sometimes
      • Crashes often
      • Vulnerable - buffer overflow...
      • Presently seems ok
    • Feedback work level:
      • Superficially; can start up and shut down
      • some crucial features
      • many crucial features
      • most crucial features
      • all features
    • Designed to work with this fundamental distribution with the version number/revision:
      • Unstable
      • Testing
      • Stable
    • ...

A package management system should also suggest un-installation of unused packages.

The primarily/non-dispensably packages that the user needs should have been marked - either explicitly or semi-automatically. If the user or an package upgrade make some packages unused, they should be suggested to be uninstalled.