Richard Purdie schrieb am Fr 28. Feb, 10:20 (+0000): > 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.
But it controls if other packages (e.g. systemd) enable pam support or not. The same goes with ldconfig: Should ldconfig support in the packages be enabled (which would pull-in ldconfig as dependency). > 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. If the feature is only about enabling code in the postinst script, than we should find a better description of the feature | ldconfig: Include support for ldconfig and ld.so.conf on the target. https://docs.yoctoproject.org/ref-manual/features.html > Packages being installed or not is an image level decision, not distro > level. Yes, that's also my understanding. But enabling some features (e.g. x11 support) leads to recipes set DEPENDS on libs and this leads to the installation of some packages. So DISTRO_FEATURES influence indirectly what gets into the image. > In this case, perhaps we should drop the RDEPENDS to a RRECOMMENDS? This would be helpful to remove ldconfig, if django is installed. But the main question is still open: Why should I want ldconfig and remove it from DISTRO_FEATURES? What is this use case? Regards Jörg -- Navimatix GmbH T: 03641 - 327 99 0 Tatzendpromenade 2 F: 03641 - 526 306 07745 Jena www.navimatix.de Geschäftsführer: Steffen Späthe, Jan Rommeley Registergericht: Amtsgericht Jena, HRB 501480
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#212056): https://lists.openembedded.org/g/openembedded-core/message/212056 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]] -=-=-=-=-=-=-=-=-=-=-=-
