Hi all,
I've noticed recently that the -f option, which specifies an alternative
configuration file, does not cause opkg to ignore configuration files in
/etc/opkg - these are apparently always read. Is this desirable behaviour?
It's certainly inconvenient within an OpenEmbedded context - after we
install the default config file into ${ROOTFS}/etc/opkg, opkg can start
behaving differently due to the altered configuration.
Cheers,
Paul
-----
Paul Eggleton
Intel Open Source Technology Centre