Move PackageFixedDeps from Cabal to cabal-install
The fundamental difference between Cabal and cabal-install is that the former deals with installed libraries, and -- in principle -- knows about _library_ dependencies only, whereas the latters deals with setup, executable, test-suite and benchmark dependencies in addition to library dependencies. Currently we classify all of these simply as 'dependencies' but that will change shortly. In this commit we take a first step towards this by moving the PackageFixedDeps class, which deals with dependencies of packages rather than installed libraries, from Cabal to cabal-install. The commit is pretty simple; we just move the type class and update import statements where necessary.
Showing
- Cabal/Distribution/Package.hs 0 additions, 11 deletionsCabal/Distribution/Package.hs
- Cabal/Distribution/Simple/GHC/IPI641.hs 1 addition, 1 deletionCabal/Distribution/Simple/GHC/IPI641.hs
- Cabal/Distribution/Simple/GHC/IPI642.hs 1 addition, 1 deletionCabal/Distribution/Simple/GHC/IPI642.hs
- cabal-install/Distribution/Client/Dependency/TopDown.hs 3 additions, 2 deletionscabal-install/Distribution/Client/Dependency/TopDown.hs
- cabal-install/Distribution/Client/Dependency/TopDown/Constraints.hs 3 additions, 2 deletions...all/Distribution/Client/Dependency/TopDown/Constraints.hs
- cabal-install/Distribution/Client/Dependency/TopDown/Types.hs 3 additions, 1 deletion...l-install/Distribution/Client/Dependency/TopDown/Types.hs
- cabal-install/Distribution/Client/Install.hs 3 additions, 1 deletioncabal-install/Distribution/Client/Install.hs
- cabal-install/Distribution/Client/InstallPlan.hs 3 additions, 1 deletioncabal-install/Distribution/Client/InstallPlan.hs
- cabal-install/Distribution/Client/PackageIndex.hs 12 additions, 1 deletioncabal-install/Distribution/Client/PackageIndex.hs
- cabal-install/Distribution/Client/Types.hs 2 additions, 2 deletionscabal-install/Distribution/Client/Types.hs
Loading
Please register or sign in to comment