Skip to content
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

Open
uhbif19 opened this issue May 29, 2024 · 4 comments
Open

Feature request: publish package on CHaP #673

uhbif19 opened this issue May 29, 2024 · 4 comments

Comments

@uhbif19
Copy link

uhbif19 commented May 29, 2024

Manually specifying GitHub source in cabal.project complicates it, leads to dependency incompatibilities and prevents plutarch dependencies from being published on CHaP themselves.

@L-as
Copy link
Member

L-as commented May 29, 2024

I would imagine you'd have to convince the CHaP maintainers.

@uhbif19
Copy link
Author

uhbif19 commented Jun 3, 2024

@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?

@SeungheonOh
Copy link
Collaborator

We have https://github.com/mlabs-haskell/mlabs-haskell-packages though not regularly bumped. However, I can bump needed packages upon requests

@SeungheonOh
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants