OK, well, you can still get the ABI of a package in all cases (it's just not in the ID anymore.) Something like:
ezyang@sabre:~$ ghc-pkg field base-4.9.0.0 abi abi: 5e731f0a06895b09ada57a6853a117b3 Also if you have an IPID use the --ipid flag: ezyang@sabre:~$ ghc-pkg field --ipid shake-0.15.5-Clzm3aWl4tlKQLUDAtY3Kz abi abi: ab9703b6467df480a09bd2985f85d97c Hope that helps. Edward Excerpts from Joachim Breitner's message of 2016-07-09 09:35:46 -0400: > Hi, > > Am Freitag, den 08.07.2016, 17:06 -0400 schrieb Edward Z. Yang: > > The "official" reason they don't have hashes is because, > > as bundled libraries, they have special status and are thus deified > > to not have hashes. (If these IDs are opaque it shouldn't matter, > > right?!) > > well, they might be opaque, but it would be really good if they would > differ if the ABI differs. So if we change the source code (bugfix, > different flags etc.), we really really want to see a different hash, > in order to detect what other packages need to be rebuilt. Basically > our whole infrastructure relies on these hashes to identify ABIs. > > Greetings, > Joachim >
