From: "Martin Siegumfeldt" <mns@gomspace.com>
To: "Alex Stewart" <alex.stewart@emerson.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] read-only-rootfs and opkg
Date: Fri, 20 Sep 2024 05:30:09 -0700 [thread overview]
Message-ID: <17877.1726835409945994361@lists.yoctoproject.org> (raw)
In-Reply-To: <DM4PR10MB6134C9BCBAABA358F109B46294622@DM4PR10MB6134.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
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 <COMPONENT>' would indicate actuals.
Runtime moving of the meta-data from '/var/lib' to '/data-os' might be an option - at least I can't think of a better for now. Manual experiments indicates the concept functional.
Again, thanks for your ideas Alex - appreciated.
Have a nice weekend,
Martin
[-- Attachment #2: Type: text/html, Size: 704 bytes --]
prev parent reply other threads:[~2024-09-20 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 10:00 read-only-rootfs and opkg Martin Siegumfeldt
2024-09-17 15:57 ` [EXTERNAL] [yocto] " Stewart, Alex
2024-09-18 8:39 ` Martin Siegumfeldt
2024-09-18 14:49 ` [EXTERNAL] " Stewart, Alex
2024-09-20 12:30 ` Martin Siegumfeldt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17877.1726835409945994361@lists.yoctoproject.org \
--to=mns@gomspace.com \
--cc=alex.stewart@emerson.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox