On Fri, 2025-02-28 at 06:42 +0100, Jörg Sommer wrote: > Changqing Li schrieb am Fr 28. Feb, 10:56 (+0800): > > But you can't remove ldconfig if you need it. Why do you remove it? > > If you want the ldconfig feature of python3-ctype, you have to enable > ldconfig. Or at least install the package. > > Or should we downgrade the dependency to a recommendation? > > > ctypes.util.find_library need ldconfig or ld or gcc to work. No matter what > > the DISTRO_FEATURES is, we should make a package at least work once it is > > installed. > > In our image python3-ctype works without ldconfig. > > > > Quotinghttps://docs.yoctoproject.org/ref-manual/features.html: > > > > > > > ldconfig: Include support for ldconfig and ld.so.conf on the target. > > > > > > > > > @Mathieu: I think you should revert the commit 0df1318e5c, because it > > > pulls > > > in ldconfig even it is unselected in DISTRO_FEATURES. It leaves no way to > > > build without ldconfig (what was the intend of my commit). > > > > when ldconfig is disabled in DISTRO_FEATURES, if we don't want ldconfig be > > pulled in, how about just not install the package that depend on ldconfig, > > eg: python3-ctypes. > > In our case python3-ctypes is a dependency of django. > > > if revert my commit, and ldconfig is disabled in DISTRO_FEATURES, and > > python3-ctype is installed, ctypes.util.find_library will not work. > > But then you need ldconfig. Either install it with IMAGE_INSTALL or include > it in DISTRO_FEATURES. I see this the same way like other DISTRO_FEATURES > for example pam: if you want to use pam with e.g. systemd you have to > include it in DISTRO_FEATURES.
DISTRO_FEATURES are high level policy controls, not "this should be included or excluded" controls. For example "pam" controls whether the access control modules are configured/used, not whether libpam is or is not included. For ldconfig, as I remember, the distro config was about whether to include "ldconfig" calls after installing libraries and whether to use the ld cache. Packages being installed or not is an image level decision, not distro level. In this case, perhaps we should drop the RDEPENDS to a RRECOMMENDS? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#212055): https://lists.openembedded.org/g/openembedded-core/message/212055 Mute This Topic: https://lists.openembedded.org/mt/111283758/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
