Should cabal-install use text-2.0?

[ulysses4ever]

The question comes from Reddit. Perhaps it may bring some benefit? Even if only in terms of popularizing text-2.0...

[avanov]

It saves Nix build times if my dependency graphs do not have to depend on two versions of text whenever I want to try out new GHC versions (for which I need to compile most of the packages locally)

[Bodigrim]

cabal-install does not really use Text much, it can certainly relax text bounds.

[Mikolaj]

We have

text         (>= 1.2.3.0  && < 1.3) || (>= 2.0 && < 2.1),

in Cabal.cabal on branch master, so it's probably only cabal-install.cabal that is excluding text 2 and probably for no good reason.

[andreasabel]

I relaxed to text-2.0 locally, but it is not picked up by the constraint solver. AFICT, it is because we depend on Cabal-3.6:

cabal/cabal-testsuite/cabal-testsuite.cabal

Lines 112 to 117 in a97e1f1

	custom-setup
	-- we only depend on even stable releases of lib:Cabal
	-- and due to Custom complexity and ConstraintSetupCabalMaxVersion
	-- it can't be the current version
	setup-depends: Cabal == 3.6.*,
	Cabal-syntax == 3.6.*,

Forcing it with -c text >= 2.0 it is used in most places, though, cabal-plan then only shows usage of text-1.2.5.0 for Cabal-3.6.3.0 then.

UPDATE: This feature would be great for my quest:

• Flag to force the use of the latest allowed package #8387