Skip to content

Re #6125: document that glob dirs are buggy in Cabal 2.4 #8665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 14, 2023

Conversation

andreasabel
Copy link
Member

@andreasabel andreasabel commented Jan 12, 2023

Re #6125: document that glob dirs are buggy in Cabal 2.4.

cabal-version: 2.4 allows e.g. data-files: foo/**/*.txt but ** directories are only handled correctly since Cabal 3.0 (issue #6125). This information should be part of the cabal file format history documentation.

Rendering here:

Relevant CI succeeds.

@Mikolaj
Copy link
Member

Mikolaj commented Jan 12, 2023

CI is fussy today, on OSX at least. I already restarted failed jobs once (GHC 9.4.2 not found), now again, with different error (git test failure).

@andreasabel andreasabel added merge me Tell Mergify Bot to merge and removed attention: needs-review labels Jan 12, 2023
@andreasabel andreasabel self-assigned this Jan 12, 2023
@mergify mergify bot added the merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days label Jan 14, 2023
`cabal-version: 2.4` allows e.g. `data-files: foo/**/*.txt` but `**`
directories are only handled correctly since Cabal 3.0 (issue #6125).
This information should be part of the cabal file format history
documentation.
@mergify mergify bot merged commit ae8ce2c into master Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-files documentation merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge re: globbing Concerning issues with globbing file patterns
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants