looking to clarify *more* variables that depend on packaging backend
"Robert P. J. Day" <[email protected]>
| Newsgroups | org.yoctoproject.lists.docs |
|---|---|
| Message-ID | <[email protected]> |
(don't have access to my build system so i can't run a simple test.)
i'm reading the section on "Excluding Packages from an Image":
https://docs.yoctoproject.org/dev-manual/packages.html#excluding-packages-from-an-image
and we already know this sentence is inaccurate:
"Each of these variables only works with IPK and RPM package types,
not for Debian packages."
because i've already submitted a patch that corrects that for the
PACKAGE_EXCLUDE variable. but what about the other two? i can't test
but i can check the code and in the rootfs_deb.bbclass:
https://git.openembedded.org/openembedded-core/tree/meta/classes-recipe/rootfs_deb.bbclass
i can see the test for one of those variables but not the other:
python rootfs_deb_bad_recommendations() {
if d.getVar("BAD_RECOMMENDATIONS"):
bb.warn("Debian package install does not support BAD_RECOMMENDATIONS")
}
do_rootfs[prefuncs] += "rootfs_deb_bad_recommendations"
so unless there some testing done somewhere else, can i conclude
that DEB packaging *does* recognize the NO_RECOMMENDATIONS variable
but not the BAD_RECOMMENDATIONS variable? if that's true, i can whip
up a patch to fix that.
rday