-
Notifications
You must be signed in to change notification settings - Fork 85
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
Fix sdist #256
Fix sdist #256
Conversation
happy_boot = bootstrap_root </> "happy" | ||
callProcess "cabal" | ||
[ "install", "happy", | ||
"-f", "-bootstrap", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"-f", "-bootstrap", | |
"-f", "+bootstrap", |
Don't we want that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would require a pre-installed happy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No we don't
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With -f -bootstrap
we don't, with -f +bootstrap
we do. That's how this flag works, and I think you named it 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry! I wasn't loading your comments, I meant to reply to myself not rudely reply to you! 😳 😬
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is not the first time my own name for the flag has confused me 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this also confuses me.
I would think that -f +bootstrap
would do something so that this instance of happy
can build itself, whereas a -f -bootstrap
would require another (already installed) instance of happy
.
Or in other words, flag on does something special, flag off does the vanilla thing.
@int-index wrote:
These instructions shouldn't just reside in a closed PR, they need to go into Also the |
Fixes #255
The new release process is:
runhaskell ./bootstrap.hs
. This replaces.y
and.ly
files with.hs
files, which applies to:packages/frontend/src/Happy/Frontend/Parser/Bootstrapped.ly
packages/frontend/src/Happy/Frontend/AttrGrammar/Parser.ly
cabal v2-sdist all
This results in the following tarballs:
Thanks to the
./bootstrap.hs
step, thehappy-frontend-2.0.tar.gz
tarball contains*.hs
files instead ofBootstrapped.ly
andParser.ly
. This should fix the issues that the users of1.21.0
encountered.The bump to
2.0
is motivated by the split into packages. I believe it's a major change that enables the use ofhappy
as a library, so it deserves a major version bump. It does not indicate a breaking change.