Skip to content

Documentation: v1 to v2 migration guide. #6104

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

Open
phadej opened this issue Jun 23, 2019 · 8 comments
Open

Documentation: v1 to v2 migration guide. #6104

phadej opened this issue Jun 23, 2019 · 8 comments

Comments

@phadej
Copy link
Collaborator

phadej commented Jun 23, 2019

cabal-install-3.0 changelog / release notes should point out to that part of documentation as the first things.

There will be a lot of confusion when 3.0 is released, and there are no migration guide explaining how v2-build or v2-install are different from v1-build or v1-install. The QuickStart section is not the right one, as it doesn't explain the differences.

@hvr hvr added this to the 3.0 milestone Jun 27, 2019
@23Skidoo 23Skidoo self-assigned this Aug 9, 2019
@23Skidoo
Copy link
Member

23Skidoo commented Aug 9, 2019

BTW, I've started writing a 3.0 migration guide for custom Setup authors: https://github.com/haskell/cabal/wiki/3.0-migration-guide. Help appreciated...

@okeuday
Copy link

okeuday commented Sep 1, 2019

Please describe in the migration guide what to do with the v2 (Nix-style local builds) commands to get the same sandbox functionality that was present with the v1 sandbox command.

@phadej
Copy link
Collaborator Author

phadej commented Sep 3, 2019

There are no sandboxes in v2 workflows. They are unneeded.

@23Skidoo
Copy link
Member

23Skidoo commented Sep 3, 2019

Right, but the migration guide should explain why.

@GeorgeCo
Copy link

GeorgeCo commented Feb 1, 2020

I think it is important to get this into 3.2 and if possible something on ghc-pkg, if only a reference to the ghc issue: #6342

@phadej
Copy link
Collaborator Author

phadej commented May 14, 2020

I de-milestone this issue.

@phadej phadej removed this from the 3.2.0.0 milestone May 14, 2020
@okeuday
Copy link

okeuday commented May 14, 2020

Still not seeing how to use local filesystem dependencies without sandboxes. I noticed that compiling cabal-install 3.2.0.0 with GHC 8.10.1 required manually fixing dependency versions in bootstrap.sh (cabal-install 3.0.0.0 had a similar problem), so Cabal 3 still needs more testing?

@ulysses4ever
Copy link
Collaborator

I think this ship has sailed. Let's close this umbrella issue and solicit concrete improvements (like description of how v2 replace sandboxes) if anyone is interested?

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

No branches or pull requests

6 participants