[yocto] OPKG configuration questions

[Trevor Woerner]

On 16 October 2013 18:19, Glenn Schmottlach <gschmottlach at gmail.com> wrote:
> One thing
> that did disturb me a little was that when I look in my
> <project>/build/tmp-eglibc/deploy/ipk is see the following:
>
>   4 drwxr-xr-x 6 gschmottlach gschmottlach   4096 Oct 16 16:38 .
>   4 drwxr-xr-x 8 gschmottlach gschmottlach   4096 Oct  3 05:53 ..
>  12 drwxr-xr-x 2 gschmottlach gschmottlach  12288 Oct 16 16:38 all
> 176 drwxr-xr-x 2 gschmottlach gschmottlach 176128 Oct 16 16:38
armv7a-vfp-neon
>  24 drwxr-xr-x 2 gschmottlach gschmottlach  24576 Oct 16 16:38
i686-nativesdk
>  40 drwxr-xr-x 2 gschmottlach gschmottlach  36864 Oct 16 16:38 nitrogen6x
>   0 -rw-rw-r-- 1 gschmottlach gschmottlach      0 Oct 16 16:38 Packages
>   0 -rw-r--r-- 1 gschmottlach gschmottlach      0 Oct  3 00:24
Packages.flock
>   4 -rw-rw-r-- 1 gschmottlach gschmottlach     20 Oct 16 16:38 Packages.gz
>   0 -rw-r--r-- 1 gschmottlach gschmottlach      0 Oct 16 16:38
Packages.stamps

Yes, I'm seeing that too.

What happens if you run (on your build machine, from your
build location) (replace stuff in <> as required):

$ <tmpdir>/sysroots/<build arch>/usr/bin/opkg-cl -o <tmpdir>/work/<target
machine>/<image>/<version>/rootfs list

For example:

$ tmp-qemuarm/sysroots/x86_64-linux/usr/bin/opkg-cl -o
tmp-qemuarm/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs
list

Does that print you a list of all the packages in your image?

Just out of curiosity, is it possible that you added "package-management"
to IMAGE_FEATURES after you already had a successful full build? Or is
it possible that you had already done a full build with "package_rpm" or
"_deb" before switching to "package_ipk"?

The reason I ask is (although I never confirmed this definitively but) when
I was playing with this stuff a while back I was sure that this package
stuff
would only get generated after adjusting these configurations when a full,
clean build was performed (i.e. removing <tmpdir> and <sstate-cache>).

If you are making changes to your build which might affect your packages
you'll need to perform:

$ bitbake package-index

Have you had a look at:
http://www.yoctoproject.org/docs/1.5/mega-manual/mega-manual.html#using-runtime-package-management

Maybe something in there might help? But it certainly sounds like you're
doing everything correctly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20131016/b4cf133b/attachment.html>