@Profpatsch note that we should include https://github.com/dhall-lang/dhall-lang/tree/master/Prelude instead of https://github.com/dhall-lang/Prelude

Now I’m extremely confused. @Gabriel439 why keep https://github.com/dhall-lang/Prelude around then?

@Profpatsch: sorry for the confusion, I'll try to clarify: we just merged the existing Prelude into the dhall-lang repo (4 days ago, here), and we didn't declare the dhall-lang/Prelude repo as discontinued yet (but it should be, and the authoritative version of the Prelude is now the dhall-lang repo)

Okay, issues have been resolved.

@Gabriel439 Are you okay with this structure in principle? Does it represent the ecosystem correctly? Because the attribute structure can’t easily be changed after the fact.

@Profpatsch: I think the only part I'm not sure about is whether there will ever be Dhall packages other than the Prelude underneath dhallPackages. It seems like in most cases people will use Dhall's built-in import system to retrieve Dhall packages rather than Nix

It seems like in most cases people will use Dhall's built-in import system to retrieve Dhall packages rather than Nix

Hm, that is true. One pro I can see with putting them into nix is that nix could “pre-compile” a dhall cache for everything in dhallPackages.