sheaf

Results 50 issues of sheaf

We have ```haskell data ProgramDb = ProgramDb { unconfiguredProgs :: UnconfiguredProgs , progSearchPath :: ProgramSearchPath , configuredProgs :: ConfiguredProgs } -- | Note that this instance does not preserve the...

type: bug
needs triage

As pointed out [here](https://gitlab.haskell.org/ghc/ghc/-/issues/18748#note_302270), attempting to unify a metavariable with a polytype can lead to rather confusing error messages, which often mention type variables which are nowhere to be seen...

`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...

type: enhancement
cabal-install: other

Users of the Cabal library API should be able to choose where Cabal output should be sent to. In `cabal-install`, we currently achieve this by using `--act-as-setup` (see `Distribution.Client.SetupWrapper.selfExecSetupMethod`): we...

type: enhancement
Cabal: other

This commit implements the Configure build-type in terms of Hooks, when build-type: Hooks is available (for Cabal >= 3.13). This moves Configure away from an implementation in terms of UserHooks,...

Cabal: custom
attention: needs-review
build-type: configure

This PR contains several commits that address problems with how we were handling unconfigured programs in the program database: - We should configure unconfigured programs before serialising them (using the...

attention: needs-review
re: --program-suffix

**Template B**: This PR does not modify behaviour or interface of `Cabal` or `cabal-install` – it is purely a change in the testsuite. This PR modifies `cabal-testsuite` to allow passing...

attention: needs-review

Quoting from `Distribution.Client.ProjectPlanning.elaborateInstallPlan.elaborateSolverToComponents`: > At this point in time, only non-Custom setup scripts are supported. > Implementing per-component builds with Custom would require us to create a new `ElabSetup` type,...

type: enhancement
cabal-install: custom

On GHC 9.0 and below we need to be able to handle flattening variables. `classifyPredType` gets us most of the way, but it'd nice to be able to directly extract...

In my opinion, the most convenient way to declare a custom preprocessor in pre-build rules (in `build-type: Hooks`) is to search for files using a file glob, and then monitor...

type: enhancement
cabal-install: other
Cabal: hooks
newcomer