Re: How to determine runtime-/build-only dependencies

OpenBSD has precompiled binary packages and

> The ports tree is meant for advanced users. Everyone is encouraged to use the pre-compiled binary packages.

> https://www.openbsd.org/faq/ports/ports.html

So there is still a distinction between build-time and runtime.

2026/01/18 23:57 Neal Gompa <[email protected]>:

On Sun, Jan 18, 2026 at 9:45 AM Rafael Sadowski <[email protected]> wrote:&#13;

>&#13;

> Hi KDE Community,&#13;

>&#13;

> I'm currently working on mapping the dependencies for the OpenBSD&#13;

> packages properly. I've started analysing the .kde-ci.yml.&#13;

>&#13;

> In OpenBSD, we have RUN_-, BUILD_- and LIB_DEPENDS. RUN_DEPENDS must&#13;

> be installed alongside the package. BUILD_DEPENDS must be present&#13;

> at build time but not linked against lib/bin and finally LIB_DEPENDS&#13;

> which link against bin/lib.&#13;

>&#13;

> Let's take a look at frameworkintegration-6.22.0 for example:&#13;

>&#13;

> We have the following LIB_DEPENDS:&#13;

>&#13;

> LIB_DEPENDS = devel/kf6/attica>=${MODKF6_VERSION} \&#13;

> devel/kf6/kcolorscheme>=${MODKF6_VERSION} \&#13;

> devel/kf6/kconfig>=${MODKF6_VERSION} \&#13;

> devel/kf6/kcoreaddons>=${MODKF6_VERSION} \&#13;

> devel/kf6/ki18n>=${MODKF6_VERSION} \&#13;

> devel/kf6/kiconthemes>=${MODKF6_VERSION} \&#13;

> devel/kf6/knewstuff>=${MODKF6_VERSION} \&#13;

> devel/kf6/knotifications>=${MODKF6_VERSION} \&#13;

> devel/kf6/kwidgetsaddons>=${MODKF6_VERSION}&#13;

>&#13;

> That's easy, because we scan all bin/libs to determined all used&#13;

> libs correctly. This This is recorded in WANTLIB. This means that&#13;

> it is immediately apparent if something is missing:&#13;

>&#13;

> WANTLIB += ${COMPILER_LIBCXX} GL KF6Attica KF6ColorScheme KF6ConfigCore&#13;

> WANTLIB += KF6CoreAddons KF6I18n KF6IconThemes KF6NewStuffCore&#13;

> WANTLIB += KF6Notifications KF6WidgetsAddons Qt6Core Qt6DBus Qt6Gui&#13;

> WANTLIB += Qt6Network Qt6Widgets c m&#13;

>&#13;

> In other words, we can correctly determine shared library dependencies, but&#13;

> now it gets exciting, but .kde-ci.yml says even more dependencies, namely:&#13;

>&#13;

> KDE_DEPENDS = devel/kf6/kconfigwidgets \&#13;

> devel/kf6/kguiaddons \&#13;

> devel/kf6/kio \&#13;

> devel/kf6/kitemviews \&#13;

> devel/kf6/oxygen-icons \&#13;

> devel/kf6/kpackage&#13;

>&#13;

> I determined KDE_DEPENDS based on kde-ci.yml. Now I'm wondering&#13;

> how to deal with it. Are these just build dependencies, or also&#13;

> runtime dependencies, or both? What's the best way to determine&#13;

> this? Can I even do that? What would be the best strategy for&#13;

> distributions?&#13;

>&#13;

&#13;

Correct me if I'm wrong, but don't ports imply that these things are&#13;

compiled on the user's computer? Doesn't that mean the distinction of&#13;

build-time and run-time is not particularly strong?&#13;

&#13;

&#13;

&#13;

-- &#13;

真実はいつも一つ！/ Always, there's only one truth!&#13;