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
I am trying to use a project that depends on something that is built with a custom build that leverages a project called superdoc. It is basically a project to augment the allowed markup within haddock blocks. Currently, this project (easyrender) is built using cabal, as is superdoc. But, I don't think that is the relevant problem, and I have created what I believe to be a minimal example. For reference - if you download superdoc, put in a stack.yaml with a few extra-dependencies, then it builds just fine, even though it uses itself to bootstrap its own custom build. So, I believe this is only an issue if you are trying to use a custom build script that is a dependency.
In this case, the reason that this is necessary is because extra-deps are currently treated similarly as local packages, and are installed to the local database. Another way this will be fixed is by unifying extra-deps and snapshots - #1265 .
I am trying to use a project that depends on something that is built with a custom build that leverages a project called superdoc. It is basically a project to augment the allowed markup within haddock blocks. Currently, this project (easyrender) is built using cabal, as is superdoc. But, I don't think that is the relevant problem, and I have created what I believe to be a minimal example. For reference - if you download superdoc, put in a stack.yaml with a few extra-dependencies, then it builds just fine, even though it uses itself to bootstrap its own custom build. So, I believe this is only an issue if you are trying to use a custom build script that is a dependency.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: