Skip to content

Commit

Permalink
Remove zlib flags from cabal.project.freeze
Browse files Browse the repository at this point in the history
  • Loading branch information
@lierdakil
lierdakil committed May 4, 2024
1 parent 6c78014 commit e9a92b6
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 2 deletions.
2 changes: 1 addition & 1 deletion Makefile
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ stack.yaml: cabal.project.freeze stack.template.yaml
echo "# THIS FILE IS GENERATED, DO NOT EDIT DIRECTLY" > stack.yaml
cat stack.template.yaml >> stack.yaml
grep -Ev 'any\.(ghc-boot-th|ghc-prim|rts|base) ' cabal.project.freeze \
| sed -rn 's/^\s*any.(.*) ==(.*),$$/- \1-\2/p' \
| sed -rn 's/^\s*any.(.*) ==([^,]*),?$$/- \1-\2/p' \
>> stack.yaml

flake.lock: .github/workflows/haskell.yml
Expand Down
1 change: 0 additions & 1 deletion cabal.project.freeze
View file
Original file line number Diff line number Diff line change
Expand Up @@ -305,5 +305,4 @@ constraints: any.Cabal ==3.10.3.0,
any.zip-archive ==0.4.3.2,
zip-archive -executable,
any.zlib ==0.7.1.0,
zlib -bundled-c-zlib +non-blocking-ffi +pkg-config
index-state: hackage.haskell.org 2024-05-04T16:06:31Z

1 comment on commit e9a92b6

@lierdakil
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To add some context for posterity, +pkg-config is not applicable on Win32, thus this messes with CI. The simpler approach is to just let cabal figure out the flags, it's not like this affects a lot to begin with. The main reason for the freezefile is to have come consistency wrt package versions between different CI jobs, and to avoid pointlessly rebuilding everything whenever some random dependency bumps version constraints.

Please sign in to comment.