You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2019. It is now read-only.
The initial PR of merging cabal2build into Hazel has a workaround for happy and alex w.r.t. data files:
Quoting /pull/3 :
Note: this PR manually checks in the data-files that Happy and Alex use
and which are generated automatically by their custom Setup.hs scripts.
Figuring out a better solution is TODO; however, those files' interfaces
have been very stable, and upcoming releases of those packages
will include them, so I think this is OK for now.
Look for a less janky approach. For example:
pier generates them manually by copying the logic in the Setup scripts
Run the Setup script enough to build the package and then extract the data files
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From internal issue tracker:
The initial PR of merging cabal2build into Hazel has a workaround for happy and alex w.r.t. data files:
Quoting /pull/3 :
Look for a less janky approach. For example:
The text was updated successfully, but these errors were encountered: