You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
finalCheckPackage (and thus checkPackageProblems) currently performs several different kinds of check on the package:
checks on the level of the GenericPackageDescription, such as the checks in checkGenericPackageDescription
checks on the PackageDescription that may have had hooks applied (either via the old UserHooks, or new SetupHooks).
This ticket tracks splitting up this logic, so that all the checks on the level of the GenericPackageDescription are done as early as possible within cabal-install (as early as it makes sense to do them; perhaps in project planning). The remaining checks would only need to check information modified by the hooks, but would thus need to be done later, after hooks have been applied (in the case of SetupHooks, after we have configured the package and its components).
The text was updated successfully, but these errors were encountered:
finalCheckPackage
(and thuscheckPackageProblems
) currently performs several different kinds of check on the package:GenericPackageDescription
, such as the checks incheckGenericPackageDescription
PackageDescription
that may have had hooks applied (either via the oldUserHooks
, or newSetupHooks
).This ticket tracks splitting up this logic, so that all the checks on the level of the
GenericPackageDescription
are done as early as possible withincabal-install
(as early as it makes sense to do them; perhaps in project planning). The remaining checks would only need to check information modified by the hooks, but would thus need to be done later, after hooks have been applied (in the case ofSetupHooks
, after we have configured the package and its components).The text was updated successfully, but these errors were encountered: