Stdlib migration issues (original) (raw)

For ease of searching: list of bot PRs (checked first ~100 until pyranha-feedstock)

• Fix corner case in stdlib piggyback #2317
• pagmo failing for stdlib minimigrator #2322 / Fix more corner cases in stdlib migrator #2327
• don't add stdlib to metapackages (see discussion here)
• spurious selectors added to stdlib (see here) (fix in More stdlib fixes #2329)
• conda-forge/mgis-feedstock@1a37a4f did not actually add {{ stdlib("c") }}. (fix in More stdlib fixes #2329)
• do not add stdlib to outputs without compilers #2330

A larger point of discussion came up in #2327 - in general we only want to add stdlib where there's a compiler already in use. However, there could be cases lurking where feedstocks are "working" right now, but not actually propagating compiler run-exports correctly.

One particular such candidate is having a global build stage and then individual outputs that don't build anything anymore, but just pick pieces out of what the global stage produced. In such a case, if run-exports are not forwarded from the global stage to the outputs, then we would create packages with incorrect constraints, unless we defensively add {{ stdlib("c") }} to those outputs as well (which is what #2135 did).