We will need to add a new variable to the list for an added feature: REMOVE_PKG_SUPPORT For images not containing a package manager, this allows the removal of supporting packages. Packages that will be uninstalled include: update-rc.d, base-passwd, shadow and update-alternatives. Set the variable to "1" to remove these packages.
Sorry, I missed one package from that list. The list should be: update-rc.d, base-passwd, shadow, run-postinsts, and update-alternatives.
Hi, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-REMOVE_PKG_SUPPORT for the new entry in the glossary. Let me know if this is okay. Thanks, Scott
Looks great! Thanks Scott.
Thanks Stephano, Bug 9491 is blocking this so I won't change the status at this point. Scott
Hey Scott, Actually, do hold off on this. I just had a meeting regarding 9491 and we're going to be changing the name and probably the text of this as well. I'll send over the changes when they are ready. Stephano
Scott - can you revert this commit (95b740d719a7a6ffe3a06a1f152af4d877ee08c7) so the documentation doesn't talk about variables that don't exist?
Ross, Sorry about that... I jumped the gun on this one. I will revert it. See http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/commit/?id=094ea24b03f92594e6e5d145b58c49ef5d8edfd7. Scott
This is ready to go now. The variable name / description is as follows: FORCE_RO_REMOVE Setting this variable to "1" will force the removal of the packages listed in ROOTFS_RO_UNNEEDED during the generation of the rootfs.
Hi, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-FORCE_RO_REMOVE for the new variable description. Note that this variable description introduces the ROOTFS_RO_UNNEEDED variable, which is not in the manual. Do we want to document that variable as well in the glossary? If so, can you provide a baseline description of it for me? If you provide a description, could you also provide a use-case example that I could use in the entry? Thanks, Scott
ROOTFS_RO_UNNEEDED cannot be easily overwritten by the end user and we don't want to give them the impression that it is something they should be editing if they want to remove packages. That could be both dangerous and confusing. Also since the contents of that list can change with each new release, it would be a pain to have to keep that up to date. I say leave it out of the manual and see if anyone complains. I doubt they will.
Perfect.. thanks. How does the description look to you otherwise? Scott
Yep, looks perfect.
Thanks, I am setting the bug to RESOLVED and putting the doc flag to "done." Scott