topdir.mk: Remove --skip-excluded from install targets #150
Loading…
Reference in a new issue
No description provided.
Delete branch "jan/fix/20261018-topdir-mk-remove-skip-excluded-from-install-targets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
topdir.mk: Remove --skip-excluded from install targets
Using
--skip-excludedin pkg-install-*'s recipes breaks CI, and here's how: During a CI run, a package is expected to be testable with onlyjw-pkgand the package itself installed in the test environment.testablehere means that it's possible to install the necessary dependencies with make pkg-install-* commands before building. That condition is inherently always met by packages which have onlyjw-pkgas its only dependency. But it's not true for packages with intermediate packages in their dependency tree. For for those packages it's not advisable to pass--skip-excludedto the dependency detection, because that will cause the resolver to try and find the intermediate'sproject.confto read its [build].excluded section. Which fails because that intermediate is neither installed nor checked out.So, until there's another mechansim in place which allows excluding uninstalled packages (caller-supplied knowledge, reading remote repositories, package-manager-like package metadata cache), drop
--skip-excludedfrom the pkg-install-* targets' recipes.a3186489e62d0544743a