Closed
Description
As we saw in IntersectMBO/cardano-db-sync@a7cd5db, we need to be very carful in the order in which overlays are applied. We want our musl/android/... platform specific overlays to be applied last. However if we provide them as haskell-nix.overalys, and people are free to mix and match, we can end up in a situation where someone inadvertently overrides one of our platform customisations. This then leads to hard to debug and surprising behaviour.