-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: publish package on CHaP #673
Comments
I would imagine you'd have to convince the CHaP maintainers. |
@L-as I was under impression that it is partially automated and open-source after reading their README. Did they have something against publishing other packages before? |
We have https://github.com/mlabs-haskell/mlabs-haskell-packages though not regularly bumped. However, I can bump needed packages upon requests |
Also, I'm wondering, instead of having a singular, centralized haskell package-set, would it be plausible to have hackage set per project. This would work more or less identically as having each repository added to cabal.project, but haskell.nix won't freak out and not cache the binary. |
Manually specifying GitHub source in
cabal.project
complicates it, leads to dependency incompatibilities and prevents plutarch dependencies from being published on CHaP themselves.The text was updated successfully, but these errors were encountered: