Modulecabal-install-3.12.1.0Haskell2010

Distribution.Client.FetchUtils

Functions for fetching packages

1 type
9 values

Packagecabal-install-3.12.1.0
Exports10
LanguageHaskell2010
LicenceBSD-3-Clause
SourceFetchUtils.hs

fetching packages

3 declarations

valuefetchPackage

Fetch a package if we don't have it already.

valueisFetched :: UnresolvedPkgLoc -> IO Bool

Returns True if the package has already been fetched or does not need fetching.

valuecheckFetched :: UnresolvedPkgLoc -> IO (Maybe ResolvedPkgLoc)

Checks if the package has already been fetched (or does not need fetching) and if so returns evidence in the form of a PackageLocation with a resolved local file location.

specifically for repo packages

valuecheckRepoTarballFetched :: Repo -> PackageId -> IO (Maybe FilePath)

Like checkFetched but for the specific case of a RepoTarballPackage.

valuefetchRepoTarball

:: Verbosity
-> RepoContext
-> Repo
-> PackageId
-> IO FilePath

Fetch a repo package if we don't have it already.

valueverifyFetchedTarballs

:: Verbosity
-> RepoContext
-> Repo
-> [PackageId]
-> IO [Either (Repo, PackageId) (Repo, PackageId)]

fetching packages asynchronously

valueasyncFetchPackages

:: Verbosity
-> RepoContext
-> [UnresolvedPkgLoc]
-> AsyncFetchMap -> IO a
-> IO a

Fork off an async action to download the given packages (by location).

The downloads are initiated in order, so you can arrange for packages that will likely be needed sooner to be earlier in the list.

The body action is passed a map from those packages (identified by their location) to a completion var for that package. So the body action should lookup the location and use waitAsyncFetchPackage to get the result.

Synchronous exceptions raised by the download actions are delivered via waitAsyncFetchPackage.

valuewaitAsyncFetchPackage

Expect to find a download in progress in the given AsyncFetchMap and wait on it to finish.

If the download failed with an exception then this will be thrown.

Note: This function is supposed to be idempotent, as our install plans can now use the same tarball for many builds, e.g. different components and/or qualified goals, and these all go through the download phase so we end up using waitAsyncFetchPackage twice on the same package. C.f. #4461.

typetype AsyncFetchMap = Map UnresolvedPkgLoc (MVar (Either SomeException ResolvedPkgLoc))

fetching other things

1 declaration

valuedownloadIndex

Downloads an index file to [config-dirpackagesserv-id] without hackage-security. You probably don't want to call this directly; use updateRepo instead.