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

Publish to Hackage/Stackage. #16

Open
Qinka opened this issue Jun 1, 2019 · 3 comments
Open

Publish to Hackage/Stackage. #16

Qinka opened this issue Jun 1, 2019 · 3 comments
Labels
blocked infrastructure Items relating to packaging, project management, releases, etc.

Comments

@Qinka
Copy link

Qinka commented Jun 1, 2019

Is there any plan to publish on hackage and stackage?

@patrickt
Copy link
Contributor

patrickt commented Jun 1, 2019

Short answer: in the future, yes, but probably not right now.

Longer answer: In principle, a Hackage release should be trivial, but in practice there are a number of obstacles to this. Firstly, we depend on haskell-tree-sitter, which is also not yet on Hackage, and involves no fewer than nine separate packages. In addition, we are sadly many versions behind in terms of the data types that haskell-tree-sitter provides, and our code is very sensitive to changes therein due to the vagaries of the Assignment modules. In addition, we have to figure out what a good release schedule for semantic looks like, what kind of version compatibility we want to provide, and how it fits into our internal infrastructure and tooling.

This is all very important work to do, but we simply haven’t had the time to do it yet. Thanks for the reminder—I’m changing the title of this issue to reflect that it is something we want to do.

Update: we also have to get rid of our pinned dependencies.

@ch3rn0v
Copy link

ch3rn0v commented Aug 6, 2019

The longer answer mentions a number of tasks to be done. Are they outlined anywhere in a more detailed way, so that we could maybe take part in resolving them?

@patrickt
Copy link
Contributor

#136 and #111 are the blockers that I know of.

patrickt added a commit that referenced this issue Aug 19, 2019
As @mpickering pointed out, this breaks `new-repl` if you have
multiple versions of `pretty-show` in your package store.
gingerhot pushed a commit to gingerhot/semantic that referenced this issue Oct 8, 2019
As @mpickering pointed out, this breaks `new-repl` if you have
multiple versions of `pretty-show` in your package store.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked infrastructure Items relating to packaging, project management, releases, etc.
Projects
None yet
Development

No branches or pull requests

3 participants