Installing alien package

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(chg)
(chg)
Line 4: Line 4:
 
So e.g. do not use "opkg upgrade" when non-distribution (e.g. non-OM2009) repositories are included. It often breaks 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?==
+
==Solution hack?==
 
Please surround the non-distribution package (alien) install with:
 
Please surround the non-distribution package (alien) install with:
 
# Addition of the required repository
 
# Addition of the required repository

Revision as of 11:12, 26 July 2009

Problem

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 package (alien) 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 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".

Retrieved from "http://wiki.openmoko.org/index.php?title=Installing_alien_package&oldid=73311"
Personal tools

Problem

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?

Please surround the non-distribution package (alien) 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 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".