On 2012-01-26 09:36, Brian Hutchinson wrote:
Update,
I'm still not doing something right. I did a clean rebuild of
core-image-base and a tar jtvf core-image-base-beagleboard.tar.bz2
reveals opkg stuff in /var/lib/opkg only. No opkg bin.
I guess I'm still in shock over this. I mean why should I have to do
anything other than:
PACKAGE_CLASSES ?= "package_ipk"
I mean, if I specify I want package_ipk in the "Package Management
configuration" section, doesn't logic follow that the image would be
created with opkg and some sample opkg.conf files? What use is it to
generate all those .ipk's for the repository the build does without
opkg being there?
Because you asked to build an absolutely minimal root file system.
In this case, it's expected that you don't want to have opkg available.
If you still want this very minimal system *and* opkg, just add the
package management as previously instructed.
EXTRA_IMAGE_FEATURES += "package_management"
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
