Bug #169

Why doesn't an opkg-cl install default to the /etc/opkg.conf configuration file?

Added by Hammel almost 8 years ago. Updated over 7 years ago.

Status:ClosedStart date:23 Feb 2013
Priority:ImmediateDue date:
Assignee:Hammel% Done:

100%

Category:00 - Basic Build Issues
Target version:0.5.0 - Beta 1
Severity:02 - High

Description

If you install XBMCBox with opkg you have to use the -f option to use the installed configuration file for opkg. Why doesn't opkg-cl default to this configuration?

History

#1 Updated by Hammel over 7 years ago

  • Priority changed from Normal to Urgent
  • Severity changed from 03 - Medium to 02 - High

#2 Updated by Hammel over 7 years ago

  • Priority changed from Urgent to Immediate

#3 Updated by Hammel over 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

Initial review makes me think that the default opkg build expects the configuration file under /etc/opkg but the installation target places it under /etc. Either the opkg installation target should be fixed or a post build step will be required to move the configuration file to the correct directly in the target tree.

#4 Updated by Hammel over 7 years ago

  • % Done changed from 20 to 50

After looking at the source and buildroot it comes down to something really simple:

The buildroot skeleton in the pibox source tree has the opkg.conf in the wrong place. It's in etc instead of etc/opkg. So the fix is just to move the location of the conf file in the skeleton.

#5 Updated by Hammel over 7 years ago

  • % Done changed from 50 to 80

Updated in kepler's sandbox. Still need to check it in. Kepler is doing a full build right now - I'll check in changes after that completes and can be tested on the hardware.

#6 Updated by Hammel over 7 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100

Fix is tested and is working. Fix has been checked in.

Also available in: Atom PDF