Skip to content

RFC consider including identifying infos from ghc --info in nix-style hash #5116

Open
@hvr

Description

@hvr

An annoying issue when working with GHC HEAD or other custom GHCs is that they tend to have overlapping GHC version numbers if you build multiple versions of GHC on the same day.

One important identifying detail however if provided by ghc --info: the git commit id from which a GHC executable was derived, e.g.

"Project Git commit id","0156a3d815b784510a980621fdcb9c5b23826f1e"

In future, maybe Hadrian could provide additional identifying fingerprints to disambiguate different GHC builds from each other.

But I think introducing the Git commit id would already help avoiding a class of subtle ABI incompatibilties between GHC snapshots sharing the same version number.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions