Open mfansler opened 3 years ago
For certain noarch
packages I think it is expected that dependencies may be missing. I don't think we have/can/need to enforce for noarch
packages that all dependencies are there.
It could be useful though to show an indication that a given package is "available as noarch" but not actually installable on a certain platform because a dependency is missing.
There are likely more of these, but I found a case where
osx-arm64
builds exist but can never be installed due to lack of dependencies:This raises the question: Even if not testing on non-native builds, shouldn't solvability at least be verified? That is, make sure something like the above plus a
--dry-run
flag can work?Otherwise, it seems like there are blind spots that the community is left to encounter on their own, detracting from the UX.