Avoid use of parseIndexState
#1903
Conversation
The `parseIndexState` uses a very simple parser that breaks for `cabal.project` files with more complicated `index-state:` fields. This will have some drawbacks: * There will no longer be a warning in the trace output if an index state was not found. * When `hackage.nix` is bumped the plan will be recomputed even if the `index-state:` in the `cabal.project` has not changed. We do not expect this to be a problem since recomputing the plan is normally relatively fast.
|
Could we in fact just purge all the |
|
We still need it when building hackage projects. I guess we could passing a |
Do we? Won't cabal just pick HEAD if we don't do anything, which will implicitly be the latest thing in |
If you have |
|
I guess that seems not that important to me? Most projects bump |
The
parseIndexStateuses a very simple parser that breaks forcabal.projectfiles with more complicatedindex-state:fields.This will have some drawbacks:
There will no longer be a warning in the trace output if an index state was not found.
When
hackage.nixis bumped the plan will be recomputed even if theindex-state:in thecabal.projecthas not changed. We do not expect this to be a problem since recomputing the plan is normally relatively fast.