Bug #169
closed
Why doesn't an opkg-cl install default to the /etc/opkg.conf configuration file?
100%
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?
Updated by Hammel about 11 years ago
- Priority changed from Normal to Urgent
- Severity changed from 03 - Medium to 02 - High
Updated by Hammel about 11 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.
Updated by Hammel about 11 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.
Updated by Hammel about 11 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.
Updated by Hammel about 11 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.