If you build your own flir-image-sherlock image, you may try to add the "Image feature" called package-management
Add the following line to file meta-flir-base/recipes-flir/images/flir-image-sherlock.bb (or in a .bbappend):
IMAGE_FEATURES += " package-management"
(It should also be possible to add this line in conf/local.conf)
Then
bitbake flir-image-sherlock
You should now find a large number of files to inspect below build_ec201/tmp/work/ec201-oe-linux-gnueabi/flir-image/1.0-r0/rootfs/var/lib/opkg
(or build_ec201/tmp/work/ec201-oe-linux-gnueabi/flir-image-sherlock/1.0-r0/rootfs/var/lib/opkg depending on version built)
Example:
$ cat tmp/work/ec201-oe-linux-gnueabi/flir-image-sherlock/1.0-r0/rootfs/var/lib/opkg/status
Package: shadow-securetty
Version: 4.2.1-r3
Status: install ok installed
Architecture: ec201
Installed-Size: 1848
Installed-Time: 1600073972
Auto-Installed: yes
Package: gstreamer1.0-plugins-bad-stereo
Version: 1.14.4.imx-r0
Depends: gstreamer1.0 (>= 1.14.4.imx), libc6 (>= 2.27), libglib-2.0-0 (>= 2.54.3), libgstaudio-1.0-0 (>= 1.14.4.imx)
Status: install ok installed
Architecture: cortexa7hf-neon-mx7ulp
Installed-Size: 9652
Installed-Time: 1600073994
Auto-Installed: yes
...
$(Should you install the generated image into target, this database would be available to opkg utility.
Note: By doing so, you would lose additional installed opkg packages, "appkit" and "prodkit" information.)