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
Describe the feature request
Currently, Cabal-hooks rules will only be demanded under the following condition, as specified in the RFC:
A rule is considered demanded if:
it generates a Haskell module that is declared to be an autogenerated module of the component we are building, or
another rule that is itself demanded depends on the output of the rule.
[…]
The issue is, as of now, both the specification and implementation will not demand rules that produce libraries (e.g. for extra bundled libs). Originally we were worried about the relative order in which other rules would be run relative to Haskell modules – but libraries don’t matter for those considerations because they will only get included in the last step (the linking invocation).
We should rectify the specification and implementation to accept rules producing libraries, something along the lines of a new bullet like:
it generates a static or dynamic library that is declared to be an extra.(static|dynamic|bundled)-library of the component we are building, or
another rule that is itself demanded depends on the output of the rule.
Describe the feature request
Currently, Cabal-hooks rules will only be demanded under the following condition, as specified in the RFC:
A rule is considered demanded if:
another rule that is itself demanded depends on the output of the rule.
[…]
The issue is, as of now, both the specification and implementation will not demand rules that produce libraries (e.g. for extra bundled libs). Originally we were worried about the relative order in which other rules would be run relative to Haskell modules – but libraries don’t matter for those considerations because they will only get included in the last step (the linking invocation).
We should rectify the specification and implementation to accept rules producing libraries, something along the lines of a new bullet like:
another rule that is itself demanded depends on the output of the rule.
This came up in the context of a user having trouble with Cabal-hooks in Discourse: https://discourse.haskell.org/t/well-typed-blog-an-introduction-to-cabal-hooks-for-package-authors/11319/10?u=romes
The text was updated successfully, but these errors were encountered: