-
Notifications
You must be signed in to change notification settings - Fork 132
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
Publishing a library with Spago #142
Comments
The topic of "how do I publish with spago" is coming up quite often recently, so I though I'd recap the current situation:
To address your concern about people "patching dependencies": the fact that the above workflow is required (in particular I.e. for what concerns "publishing" it doesn't matter if a package compiles with spago or psc-package, it has to compile with bower. So everything is fine on this side :) The planThere are a few desiderable things that we could do (in this order):
|
Can confirm, is accurate. |
Gotcha. That addresses the concern I raised then. I know I read somewhere that packages are required to be published to the Bower registry before they can be added into the package set to avoid Haskell's problem of splitting the ecosystem. However, I don't see an explanation of that written anywhere in this project. (Maybe it was stated in the Slack chatroom?) |
Yeah this is documented in the package-sets contributing guidelines I linked above, and the explanation was purposefully left out from Spago's docs so far, as I didn't have a clear plan forward and didn't want to confuse readers. |
Makes sense.
I'm going to be nit-picky here: the words used there are "should" not "required"/"must". Until the plan gets implemented, would you mind if I submit a PR that clarifies that contributing guideline a bit more? |
Sure, I think having clear contribution guidelines in |
Ok. I'll make this a goal for the upcoming week |
Coming from @f-f's comment here (very end of the comment):
Followed by my comment here (very end of comment):
The text was updated successfully, but these errors were encountered: