I'm trying to use DEPENDS:=+wpad-mbedtls
in my custom packge, as it is needed for the automatic configuration the package generates. A build with the package selected fails with the following error:
Collected errors:
* check_conflicts_for: The following packages conflict with wpad-mbedtls:
* check_conflicts_for: wpad-basic-mbedtls *
* opkg_install_cmd: Cannot install package wpad-mbedtls.
* check_conflicts_for: The following packages conflict with wpad-mbedtls:
* check_conflicts_for: wpad-basic-mbedtls *
* opkg_install_cmd: Cannot install package kb-base-conf.
The conflict arises as wpad-basic-mbedtls
gets selected by MODULE_DEFAULT_wpad-basic-mbedtls
, which in turn gets generated by scripts/target-metadata.pl
somehow. This is because wpad-basic-mbedtls
is listed in the targets DEFAULT_PACKAGES
in target/linux/mediatek/filogic/target.mk
.
So I'm looking for the correct way to have the full wpad as dependency of my package, (preferably) without hacks in other places besides my package configuration. Are 'anti-dependencies' a thing? I could did not find them documented in 1 of 2. Or is there maybe a mechanism to 'upgrade' the wpad-basic to a full wpad with though some variable?