This allows to use more than one package adress via config file.
Example configuration in /etc/opkg/opkg.conf:
...
src packages http://www.yourserver.org/pkgs/packages
src local 192.168.1.2/pkgs/local
...
After Update, all packeges will be listed in the manager list and can
be installed, updated ...
cache dir option not required assigned in config file.
Note: existing option "cache" in opkg config file must be removed now, otherwise
it could hail error log messages and gui package listing could be garbled!
Not nice now, but it's one step for an unified configure handling.
Advanced build system can come up with an impressive list of
(sub-)packages, most of them not really interesting for installation
through the GUI. Add a filter with simple patterns to suppress the
display of those packages.
TODO: this should be made configurable via a run-time config file.
Signed-off-by: Markus Volk <f_l_k@gmx.net>
opkg-key does not work at all in standard installs (without gpg)
and is not needed for package management.
Slightly change the definition of opkg commands to not initialize
with find_executable function at startup which seems bogus.
