;pkg: stack: drop allow-newer-deps lists, they add more cost than benefit

The default build plan, working on unix, fails on windows because more
containers dependers are pulled in on that platform. In general it's
hard to discover all the dependers, and that list may change over
time. (With cabal, you list dependees instead, which is easier.)

So, don't try to restrict the dependers whose bounds can be relaxed;
just let it ignore all bounds, while still respecting the versions
pinned in extra-deps. This should work most of the time; when not,
it will give a compilation error rather than a bounds error.

Author: simonmichael

stack.yaml

@@ -19,8 +19,3 @@ extra-deps:
 - aeson-2.3.0.0
 - text-iso8601-0.2.0.0
 allow-newer: true
-allow-newer-deps:
-  - aeson-pretty
-  - http-api-data
-  - persistent
-  - yesod-test

stack910.yaml

@@ -17,10 +17,6 @@ extra-deps:
 - aeson-2.3.0.0
 - text-iso8601-0.2.0.0
 allow-newer: true
-allow-newer-deps:
-  - aeson-pretty
-  - http-api-data
-  - persistent
 
 nix:
   pure: false

stack912.yaml

@@ -18,11 +18,6 @@ extra-deps:
 - aeson-2.3.0.0
 - text-iso8601-0.2.0.0
 allow-newer: true
-allow-newer-deps:
-  - aeson-pretty
-  - http-api-data
-  - persistent
-  - yesod-test
 
 nix:
   pure: false

stack96.yaml

@@ -21,10 +21,6 @@ extra-deps:
 - character-ps-0.1
 - text-iso8601-0.2.0.0
 allow-newer: true
-allow-newer-deps:
-- aeson
-- aeson-pretty
-- persistent
 
 nix:
   pure: false

stack98.yaml

@@ -20,10 +20,6 @@ extra-deps:
 - attoparsec-aeson-2.2.2.0
 - text-iso8601-0.2.0.0
 allow-newer: true
-allow-newer-deps:
-  - aeson-pretty
-  - http-api-data
-  - persistent
 
 nix:
   pure: false