Indeed, it was from a layer-local "opkg_%.bbappend" - moving to local.conf
seems to do the trick.
Yes I would like to use opkg runtime to be able to update individual components
and also keep the meta-data updated, such that e.g. 'opkg info '
would indicate actuals.
Runtime moving of the meta-
__
From: yocto@lists.yoctoproject.org on behalf of
Martin Siegumfeldt
Sent: Wednesday, September 18, 2024 04:39
To: Stewart, Alex; yocto@lists.yoctoproject.org
Subject: [EXTERNAL] Re: [yocto] read-only-rootfs and opkg
Hi Alex, Thanks for your input - highly appreciated. It appears you have a
p
Hi Alex,
Thanks for your input - highly appreciated.
It appears you have a point regarding the variable assignment - 'bitbake-getvar
OPKGLIBDIR' indeed indicates the intended assignment does not occur:
$ bitbake-getvar --value OPKGLIBDIR
NOTE: Starting bitbake server...
/var/lib
Doing the stron
lists.yoctoproject.org on behalf of
Martin Siegumfeldt
Sent: Monday, September 16, 2024 06:00
To: yocto@lists.yoctoproject.org
Subject: [EXTERNAL] [yocto] read-only-rootfs and opkg
Hi all, I am trying to realize a rootfs backed by opkg as package manager. It
appears that the opkg meta-dat
Hi all,
I am trying to realize a rootfs backed by opkg as package manager. It appears
that the opkg meta-data is directed to a volatile mount (triggered by
read-only-rootfs feature in order to achieve write access I assume):
$ tail -5 /etc/opkg/opkg.conf
# Default destination for installed pack
