Why doesn't an opkg-cl install default to the /etc/opkg.conf configuration file?
|Status:||Closed||Start date:||23 Feb 2013|
|Category:||00 - Basic Build Issues|
|Target version:||0.5.0 - Beta 1|
|Severity:||02 - High|
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?
#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.