All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Seth Bollinger <seth.boll@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: opkg list-installed is empty
Date: Mon, 03 Jun 2013 13:10:47 +0100	[thread overview]
Message-ID: <1979845.55KWpAQeV6@helios> (raw)
In-Reply-To: <CA+JN8xP3hNL6qmi=pDJRHAnp-3d_e2Z-=2sKncUxMq2jrRAS9Q@mail.gmail.com>

Hi Seth,

On Monday 03 June 2013 06:49:06 Seth Bollinger wrote:
> I'm having a problem with opkg.  When I run the image I've built with the
> package-management feature and PACKAGE_CLASS equal to package_ipk, the
> image has no installed packages.  They're obviously installed, because it's
> running but "opkg list-installed" is empty.  I was expecting a large list
> of installed packages.  I don't see anything I would expect to see in
> /var/lib/opkg.  I must be missing something fundamental, but after
> reviewing the documentation and code, I'm coming up empty.  Please
> enlighten me!

If /var/lib/opkg is empty in your image, it can only be because its contents 
have been deleted; and that could be either because the value of 
IMAGE_FEATURES doesn't end up containing package-management, or alternatively 
remove_packaging_data_files is being added manually to 
ROOTFS_POSTPROCESS_COMMAND (as core-image-minimal does). I'd suggest using 
bitbake -e your-image | less and looking at the values of IMAGE_FEATURES and 
ROOTFS_POSTPROCESS_COMMAND to see what's really going on.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-06-03 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 11:49 opkg list-installed is empty Seth Bollinger
2013-06-03 12:10 ` Paul Eggleton [this message]
2013-06-04  1:47   ` seth bollinger

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=1979845.55KWpAQeV6@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=seth.boll@gmail.com \
    --cc=yocto@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 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.