-
-
Notifications
You must be signed in to change notification settings - Fork 397
Let cabal-ghc901.project be cabal.project.local #2241
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
Conversation
Can we just replace cabal.project with cabal-ghc901.project ? |
🤔 hmm i had not thought in this possibility, but it would be right one if it is possible, will try, thanks! |
Possible caveats:
But it worths to investigate |
But maybe we could merge this as is? merge both cabal.project is not trivial |
Other alternative is convert cabal-ghc901.project in cabal-ghc901.local and remove duplication |
I think it will be the best option, implementing |
This might break ghcup /cc @maerwald |
0c04171
to
96dc126
Compare
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.
ci.sh
needs to be fixed
Co-authored-by: Julian Ospald <[email protected]>
Co-authored-by: Julian Ospald <[email protected]>
@hasufell finally i've kept the CABAL_PROJECT in the script, maybe it is neededin the future |
I ha
ugh |
do you refer to |
it seems ci is ignoring the copied |
Not sure if the deduplication worths change the status quo: the gitlab script assumes this is the way we give support for new ghc's nd |
cp cabal-ghc901.project cabal.project.local
to make the workflow smootherallow-newer
(thanks to @gbaz for the suggestion)