Skip to content

Change recommendation: include generated cabal files #5210

Closed

Description

@snoyberg

For details of the proposal, see the blog post: https://tech.fpcomplete.com/blog/storing-generated-cabal-files

If you are in favor of this change, please press thumbs up below. If you are opposed, please press thumbs down. Of course, feel free to include additional comments below.

Activity

  1. added this to the P0: Blocking release milestone on Mar 4, 2020
  2. self-assigned this
    on Mar 4, 2020
  3. gromakovsky commented on Mar 5, 2020

    @gromakovsky

    One problem with this approach that I encountered is that rebases become more painful. We have a repo with many packages, each one has package.yaml and we store .cabal files in the repo. If someone updates .cabal file(s) in master and you update something different in .cabal files in your branch by updating package.yaml and regenerating them (e. g. you both add a new dependency), you will get unnecessary conflicts because hpack adds a line with a hash.

    It's not something critical, I just wanted to warn people about this inconvenience.

  4. cdornan commented on Mar 7, 2020

    @cdornan

    I have been getting feedback from non-stack users complaining about repos with no cabal files. From their perspective it is frustrating so I am delighted with this proposal even if it might be a little more inconvenient. N retrospect Cabal files form the basis of the package system so it is better to include them directly.

  5. snoyberg commented on Mar 8, 2020

    @snoyberg
    ContributorAuthor

    OK, I'm going to move ahead with this. Thanks for the responses all. Closing as the discussion is done, will be merged to master fairly soon.

  6. simonmichael commented on Apr 15, 2020

    @simonmichael
    Contributor

    Agreeing with gromakovsky that this can very often cause conflicts and pain when merging/cherry-picking/switching branches/trying different stack/hpack versions. I think it's worth changing hpack to fix this - if you agree, consider helping sol/hpack#380.

  7. 40 remaining items

  8. added a commit that references this issue on May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions