Hoogle Search

Within LTS Haskell 24.52 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

Exact lookup

1. type PackageSourceHash = HashValue

   cabal-install	Distribution.Client.PackageHash

   No documentation available.

2. module Distribution.Client.ParseUtils

   Parsing utilities.

3. module Distribution.Client.ProjectBuilding

   No documentation available.

4. module Distribution.Client.ProjectBuilding.PackageFileMonitor

   No documentation available.

5. data PackageFileMonitor

   cabal-install	Distribution.Client.ProjectBuilding.PackageFileMonitor

   As part of the dry run for local unpacked packages we have to check if the package config or files have changed. That is the purpose of PackageFileMonitor and checkPackageFileMonitorChanged. When a package is (re)built, the monitor must be updated to reflect the new state of the package. Because we sometimes build without reconfiguring the state updates are split into two, one for package config changes and one for other changes. This is the purpose of updatePackageConfigFileMonitor and updatePackageBuildFileMonitor.

6. PackageFileMonitor :: FileMonitor ElaboratedConfiguredPackage () -> FileMonitor (Set ComponentName) BuildResultMisc -> FileMonitor () (Maybe InstalledPackageInfo) -> PackageFileMonitor

   cabal-install	Distribution.Client.ProjectBuilding.PackageFileMonitor

   No documentation available.

7. data PackageBuildingPhase

   cabal-install	Distribution.Client.ProjectBuilding.UnpackedPackage

   Each unpacked package is processed in the following phases:

   • Configure phase
   • Build phase
   • Haddock phase
   • Install phase (copy + register)
   • Register phase
   • Test phase
   • Bench phase
   • Repl phase
   Depending on whether we are installing the package or building it inplace, the phases will be carried out differently. For example, when installing, the test, benchmark, and repl phase are ignored.

8. module Distribution.Client.ProjectConfig

   Handling project configuration.

9. data PackageConfig

   cabal-install	Distribution.Client.ProjectConfig

   Project configuration that is specific to each package, that is where we can in principle have different values for different packages in the same project.

10. PackageConfig :: MapLast String FilePath -> MapMappend String [String] -> NubList FilePath -> FlagAssignment -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag ProfDetailLevel -> Flag ProfDetailLevel -> [String] -> Flag OptimisationLevel -> Flag PathTemplate -> Flag PathTemplate -> [FilePath] -> [FilePath] -> [FilePath] -> [FilePath] -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag DebugInfoLevel -> Flag DumpBuildInfo -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag String -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag Bool -> Flag FilePath -> Flag Bool -> Flag Bool -> Flag FilePath -> Flag PathTemplate -> Flag PathTemplate -> Flag String -> Flag String -> Flag FilePath -> Flag HaddockTarget -> Flag PathTemplate -> Flag PathTemplate -> Flag TestShowDetails -> Flag Bool -> Flag FilePath -> Flag Bool -> [PathTemplate] -> [PathTemplate] -> PackageConfig

    cabal-install	Distribution.Client.ProjectConfig

    No documentation available.

Page 1240 of many | Previous | Next