Add the following to the local.conf: EXTRA_IMAGE_FEATURES += "doc-pkgs" It is expected that this will install all the -doc packages to the target file system, much like adding "dbg-pkgs" would add the debug-info packages to the target file system. It does not appear as if the if the doc-pkgs is plumbed all the way throught the RECOMMENDS... in the same manner as the dbg-pkgs and dev-pkgs.
RFC patches need rework, moving to M3. Will be done early M3
Patches are now out on the OE-core list for review on this one (for merging into M3 rather than M2).
Implemented in the following commits: fa5640d143beea4be101d6622d3fa133d04272f2 22965c47152c801fada815e0b165050e8e7f9549 ad63b9b11b4c42414ff2c180dd03c1a7283321ec
Addendum: the following fix was just merged to avoid errors installing locale packages for recipes that remove PN from PACKAGES after the above fixes (affecting gcc-runtime): 06ad59cca92f58d4eefa42b532a778f3b83c66a1
Hello Paul, I am reopening this are there are no doc packages installed for core-image-sato when using the option from the description. If there is another way to test or my test is invalid, please let me know. Laurentiu
Hi Laurentiu, I just tested it here and it worked perfectly - I did nothing more than adding EXTRA_IMAGE_FEATURES += "doc-pkgs" to my conf/local.conf and then bitbake core-image-sato. Some questions: 1) How are you verifying that no doc packages are installed? 2) Which packaging backend are you using? 3) Is doc-pkgs listed when you run the following command: bitbake -e core-image-sato | grep ^IMAGE_FEATURES
Hello Paul, Although I added the line EXTRA_IMAGE_FEATURES += "doc-pkgs" in the local.conf the output of bitbake -e core-image-sato is lserban@computer2:~/work/master/build$ bitbake -e core-image-sato | grep IMAGE_FEATURES | grep EXTRA # EXTRA_IMAGE_FEATURES=debug-tweaks EXTRA_IMAGE_FEATURES="debug-tweaks" What is interesting is that the doc packages are built but not added to the image. The packages are rpm
Found the issue, There was another EXTRA_IMAGE_FEATURES +=Xxxx overwriting the initial one. I will retested and change the state.
Right, that would explain it (although it would need to be = and not += to have behaved in the way described). FYI, to answer your other comment, the doc packages are always produced by default for any recipe which installs files into documentation directories (see the value of FILES_${PN}-doc in meta/conf/bitbake.conf). Not all packages do this however. This is independent of whether the doc packages get installed into the image.
Thank you for the info Paul I will close this
Setting to verified
For reference, I missed noting one more change that is required for this functionality to work - poky revision 5334a93d261598757ccce48a78b8ba2b7e5806f3.