From: "Andreas Müller" <schnitzeltony@googlemail.com>
To: openembedded-devel@lists.openembedded.org
Subject: IMAGE_FEATURES questions (was [meta-oe][RFC 00/27] systemd / initmanager rework)
Date: Wed, 8 Feb 2012 11:40:52 +0100 [thread overview]
Message-ID: <CALbNGRT=M=x7dTr68hLVs37ZAOQ1EOerAn+AbbXveAz6AMcABg@mail.gmail.com> (raw)
On Tue, Feb 7, 2012 at 5:39 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Tue, Feb 7, 2012 at 14:35, Andreas Müller
> <schnitzeltony@googlemail.com>wrote:
>
>> On Tue, Feb 7, 2012 at 4:12 PM, Andreas Müller
>> <schnitzeltony@googlemail.com> wrote:
>> > What I have already
>> > detected after a build from scatch is that /var/lib/opkg is missing in
>> the
>> > image (although it can be found in libopkg.ipk).
>> Hmm Last night I had a build from scratch without these patches and
>> have the same - this seems a different issue...
>
>
> You need to add package-management onto IMAGE_FEATURES or it will be
> dropped if all postinst has runned fine in rootfs generation.
>
I added into my image
IMAGE_FEATURES += "package-management"
and after rebuild find the missing directories in my image. Looking
around in my environment gives:
* angstrom sets
meta-angstrom/conf/distro/include/angstrom-core-tweaks.inc:EXTRA_IMAGE_FEATURES
??= "package-management"
* in my local.conf I have (taken from OE-core local.conf.sample - long
time ago) EXTRA_IMAGE_FEATURES = "debug-tweaks"
* EXTRA_IMAGE_FEATURES is added to IMAGE_FEATURES in bitbake.conf.
If I understand this right, the angstrom default is kicked out by my
local.conf. Since I use this configuration for a while now: What has
changed causing the directories missing?
Andreas
next reply other threads:[~2012-02-08 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 10:40 Andreas Müller [this message]
2012-02-08 10:51 ` IMAGE_FEATURES questions (was [meta-oe][RFC 00/27] systemd / initmanager rework) Otavio Salvador
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='CALbNGRT=M=x7dTr68hLVs37ZAOQ1EOerAn+AbbXveAz6AMcABg@mail.gmail.com' \
--to=schnitzeltony@googlemail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.