Kristen Kozak
Kristen Kozak
Thanks for the feedback! > Per-component occurs if and only if: > > We are new-build > build-type is not Custom > cabal-version >= 1.8 > --disable-per-component is not specified...
After #4884 and #5304, the solver stores the two components that are involved in each dependency. The dependent component is a [`D.Solver.Types.ComponentDeps.Component`](https://github.com/haskell/cabal/blob/898fcc230fb537064f0992cfffb5955b6bc36d34/cabal-install/Distribution/Solver/Types/ComponentDeps.hs#L53), and the depended upon component is a [library...
I'm less familiar with the change that would be required to allow cycles between packages, but I think it could be implemented separately from the other parts of this feature,...
> > Should we only relax cycle detection for tests and benchmarks for now? > > I think the idea is that the cycles really and actually go away once...
@isovector None of the changes to cycle detection have been implemented yet, so we could definitely use a hand! I gave a summary of what I think needs to be...
> A pinch of optimism: a design was laid out long time ago: https://github.com/haskell/cabal/issues/4087#issuecomment-287665861 Someone just needs to put the time to realize it. Yes, there is a design, and...
I think this is the same feature as #9558.
Could the field just be called `constraints`, since the listed packages aren't treated as dependencies?
Yeah, that would also work. Is it okay if existing packages fail the check?
I wasn't planning on fixing this soon.