Skip to content
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

ghc-filesystem: use same config file name even before 1.5.2 #9383

Merged

Conversation

SpaceIm
Copy link
Contributor

@SpaceIm SpaceIm commented Feb 14, 2022

Before 1.5.2, no config file was generated upstream, it was just broken: see gulrak/filesystem#93.
So there is no reason to use a different config file name if version is lower than 1.5.2 in conan generators like I did in #9238.
Therefore I propose to use the same config file name to make things simpler and coherent.


  • I've read the guidelines for contributing.
  • I've followed the PEP8 style guides for Python code in the recipes.
  • I've used the latest Conan client version.
  • I've tried at least one configuration locally with the
    conan-center hook activated.

Indeed, before 1.5.2, no config file was generated upstream, it was just broken. So there is no reason to use a different config file name in conan generators. Therefore we use the same config file name to make things simpler and coherent.
@conan-center-bot
Copy link
Collaborator

All green in build 1 (b4f77796f1d83b2b61bc796c173ef23dafb9f42e):

  • ghc-filesystem/1.4.0@:
    All packages built successfully! (All logs)

  • ghc-filesystem/1.5.8@:
    All packages built successfully! (All logs)

@conan-center-bot conan-center-bot merged commit d892892 into conan-io:master Feb 15, 2022
@SpaceIm SpaceIm deleted the ghc-filesystem-one-config-file branch February 15, 2022 21:59
SSE4 pushed a commit to madebr/conan-center-index that referenced this pull request Feb 21, 2022
… 1.5.2

Indeed, before 1.5.2, no config file was generated upstream, it was just broken. So there is no reason to use a different config file name in conan generators. Therefore we use the same config file name to make things simpler and coherent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants