Add ComponentSetup to ComponentDeps
Although we don't use the new setup dependency component anywhere yet, I've replaced all uses of CD.flatDeps with CD.nonSetupDeps. This means that when we do introduce the setup dependencies, all code in Cabal will still use all dependencies except the setup dependencies, just like now. In other words, using the setup dependencies in some places would be a conscious decision; the default is that we leave the behaviour unchanged.
Showing
- cabal-install/Distribution/Client/BuildReports/Storage.hs 2 additions, 2 deletionscabal-install/Distribution/Client/BuildReports/Storage.hs
- cabal-install/Distribution/Client/ComponentDeps.hs 29 additions, 0 deletionscabal-install/Distribution/Client/ComponentDeps.hs
- cabal-install/Distribution/Client/Configure.hs 2 additions, 2 deletionscabal-install/Distribution/Client/Configure.hs
- cabal-install/Distribution/Client/Dependency/Modular/ConfiguredConversion.hs 1 addition, 1 deletion...ibution/Client/Dependency/Modular/ConfiguredConversion.hs
- cabal-install/Distribution/Client/Dependency/TopDown/Types.hs 2 additions, 2 deletions...l-install/Distribution/Client/Dependency/TopDown/Types.hs
- cabal-install/Distribution/Client/Install.hs 4 additions, 4 deletionscabal-install/Distribution/Client/Install.hs
- cabal-install/Distribution/Client/InstallPlan.hs 3 additions, 3 deletionscabal-install/Distribution/Client/InstallPlan.hs
- cabal-install/Distribution/Client/InstallSymlink.hs 1 addition, 1 deletioncabal-install/Distribution/Client/InstallSymlink.hs
- cabal-install/Distribution/Client/PlanIndex.hs 7 additions, 7 deletionscabal-install/Distribution/Client/PlanIndex.hs
- cabal-install/Distribution/Client/Types.hs 1 addition, 1 deletioncabal-install/Distribution/Client/Types.hs
Loading
Please register or sign in to comment