Ross, My local.conf is the same for all builds. The only thing is beaglebone and pandaboard are using meta-ti which require a chg to bblayer.conf. All generate a different kernel beagleboard 3.4.36 qemuarm 3.8.4 beaglebone 3.2.28 pandaboard 3.4.11 Also all are using meta-yocto = "master:068085f79010e3db70085d4b789f84ae721e4901" I have seen the rpm -qa that is where I noticed the different number of pkgs installed. They all use EXTRA_IMAGE_FEATURES = "debug-tweaks tools-sdk".in local.conf Something within the build is deciding which pkgs get installed between different builds. I would expect several different RPMs but not hundreds as was the case. Thanks
On Tue, Apr 16, 2013 at 8:03 AM, Burton, Ross <ross.bur...@intel.com> wrote: > On 16 April 2013 15:01, Edward Vidal <vidal.devel...@gmail.com> wrote: > > I did a search for installed-pkgs.txt and complementary-pkgs.txt neither > of > > these files were on my system. I am assuming this is because in my > > local.conf I am using INHERIT += "rm_work". > > as found on page 41 of the ref_manual. What is the difference between > the > > two pkgs sets? The does reduce the capabilities of the systems? Can the > > complementary-pkgs.txt be installed with a flag? > > Yes, rm_work will delete those files. > > As far as I know, "installed" is the packages explicitly installed, > "complementary" is the set installed through features such as > dev-pkgs. > > If you really want to find the differences on these images, boot each > and dump the installed package list (rpm -qa?). > > Ross >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
