Add a developer script which automates the process of hosting an OE build's deploy/IPKs tree on the network, which makes it faster to test out IPK changes on real hardware and VMs.
[0] usr0:dev$ ./host_deploy_ipks -h
usage: host_deploy_ipks [-h] [--verbose] [--version] [-b [BIND]] [-e] [-p [PORT]] [--suppress-opkg-conf] [root]
Host an OE IPK deploy tree on an HTTP server.
positional arguments:
root The root path for the feed server. (Default=${PWD})
options:
-h, --help show this help message and exit
--verbose, -v Increase the verbosity of script output. Specify once for verbose output, specify twice for debug.
--version, -V Print his script's version information and exit.
-b [BIND], --bind [BIND]
The host address to which the feed server should bind. (Default=0.0.0.0)
-e, --host-empty If asserted, host IPK feeds that contain no packages.
-p [PORT], --port [PORT]
The port number over which the feed server will host. (Default=8080)
--suppress-opkg-conf If enabled, do not print an opkg conf script.
After which, you can copy-paste the snippet into a target's shell and install opkg packages to your contentment. (Provided your dev machine's hostname is resolvable from the target.)
Send ^C to stop the feed server.
Testing
[x] Tested the script from my dev machine with a QEMU VM. After adding my QEMU host to the guest like echo "10.0.2.2 41d17" >>/etc/hosts (only needed to make QEMU SLiRP networking work), I can trivially install IPKs from the hosted feed.
Add a developer script which automates the process of hosting an OE build's deploy/IPKs tree on the network, which makes it faster to test out IPK changes on real hardware and VMs.
Invocations look like:
After which, you can copy-paste the snippet into a target's shell and install opkg packages to your contentment. (Provided your dev machine's hostname is resolvable from the target.)
Send
^C
to stop the feed server.Testing
echo "10.0.2.2 41d17" >>/etc/hosts
(only needed to make QEMU SLiRP networking work), I can trivially install IPKs from the hosted feed.