Post AaYru7tDBtfxtpAhKy by minoru@functional.cafe
 (DIR) More posts by minoru@functional.cafe
 (DIR) Post #AaYru7tDBtfxtpAhKy by minoru@functional.cafe
       2023-10-08T13:17:25Z
       
       0 likes, 0 repeats
       
       #haskell folk: how do I verify that my package can be built with bytestring 0.12? There is no GHC releases that bundle that version yet. Is there some flag that could tell it to use a version from Hackage rather than the one included into the GHC distribution?
       
 (DIR) Post #AaYru8tbRvaD1KMWaO by L29Ah@qoto.org
       2023-10-08T13:22:34Z
       
       0 likes, 0 repeats
       
       @minoru Just specify the version in the cabal file of the target package and then call cabal to install them deps?
       
 (DIR) Post #AaYsCrG3Fcn7ormpcm by minoru@functional.cafe
       2023-10-08T13:25:57Z
       
       0 likes, 0 repeats
       
       @L29Ah Why do I have to install them? Can't I make Cabal pull it from Hackage like every other dependency?I don't want to pollute my system with packages installed via Cabal. Although I think Cabal now has some sort of a sandbox, perhaps I should look into that.
       
 (DIR) Post #AaYsHNN9n8qWZzGSZc by L29Ah@qoto.org
       2023-10-08T13:26:47Z
       
       0 likes, 0 repeats
       
       @minoru Doesn't it pull them like every other dependency when you adjust your cabal file and hit `cabal build`?
       
 (DIR) Post #AaYse7iABZRkfRw94a by minoru@functional.cafe
       2023-10-08T13:30:52Z
       
       0 likes, 0 repeats
       
       @L29Ah Oops! I was specifying --constrain 'bytestring == 1.12.0.2', which failed because 1.12.0.2 doesn't exist. The error message looked just like the one I get if a dependency can't be satisfied.Thanks :)