HORIZON HASKELLDocslts/ghc-9.10.x248f8f02026-10-05Search names, modules, packages, or :: a typeCtrl K

GHC 9.10.3 · lts/ghc-9.10.x · 248f8f0 · 2026-10-05

Modulecabal-install-3.12.1.0Haskell2010

Distribution.Client.Setup

  • 19 types
  • 52 values
datadata GlobalFlags
#

Flags that apply at the top level, not to any sub-command.

Instances5Show, Generic, Semigroup, Monoid, Rep
datadata RepoContext
#

Access to repositories

Constructors

  • RepoContext
    • repoContextRepos :: [Repo]

      All user-specified repositories

    • repoContextGetTransport :: IO HttpTransport

      Get the HTTP transport

      The transport will be initialized on the first call to this function.

      NOTE: It is important that we don't eagerly initialize the transport. Initializing the transport is not free, and especially in contexts where we don't know a priori whether or not we need the transport (for instance when using cabal in "nix mode") incurring the overhead of transport initialization on _every_ invocation (eg cabal build) is undesirable.

    • repoContextWithSecureRepo :: forall a. Repo -> (forall (down :: Type -> Type). Repository down -> IO a) -> IO a

      Get the (initialized) secure repo

      (the Repo type itself is stateless and must remain so, because it must be serializable)

    • repoContextIgnoreExpiry :: Bool

      Should we ignore expiry times (when checking security)?

datadata ConfigFlags
#

Flags to configure command.

IMPORTANT: every time a new flag is added, D.C.Setup.filterConfigureFlags should be updated. IMPORTANT: every time a new flag is added, it should be added to the Eq instance

Constructors

Instances10Eq, Read, Show, Generic, Semigroup, Monoid, …

Given some ConfigFlags for the version of Cabal that cabal-install was built with, and a target older Version of Cabal that we want to pass these flags to, convert the flags into a form that will be accepted by the older Setup script. Generally speaking, this just means filtering out flags that the old Cabal library doesn't understand, but in some cases it may also mean "emulating" a feature using some more legacy flags.

datadata ConfigExFlags
#
Instances6Eq, Show, Generic, Semigroup, Monoid, Rep
datadata BuildFlags
#
Instances9Read, Show, Generic, Semigroup, Monoid, Binary, …

Given some TestFlags for the version of Cabal that cabal-install was built with, and a target older Version of Cabal that we want to pass these flags to, convert the flags into a form that will be accepted by the older Setup script. Generally speaking, this just means filtering out flags that the old Cabal library doesn't understand, but in some cases it may also mean "emulating" a feature using some more legacy flags.

datadata InstallFlags
#
Instances7Eq, Show, Generic, Semigroup, Monoid, Binary, …
datadata ListFlags
#
Instances4Generic, Semigroup, Monoid, Rep
datadata UpdateFlags
#
Instances3Generic, HasVerbosity, Rep
datadata InfoFlags
#
Instances4Generic, Semigroup, Monoid, Rep
datadata FetchFlags
#
datadata FreezeFlags
#
Instances1HasVerbosity
  • HasVerbosity FreezeFlagsDefined in cabal-install-3.12.1.0 · Distribution.Client.CmdLegacy
datadata GetFlags
#
Instances4Generic, Semigroup, Monoid, Rep
datadata UploadFlags
#
Instances4Generic, Semigroup, Monoid, Rep
datadata ReportFlags
#
Instances4Generic, Semigroup, Monoid, Rep
datadata InitFlags
#
Instances6Eq, Show, Generic, Semigroup, Monoid, Rep
datadata ActAsSetupFlags
#
Instances4Generic, Semigroup, Monoid, Rep
datadata UserConfigFlags
#
Instances4Generic, Semigroup, Monoid, Rep