Skip to content

When adding git packages, please check subdirs. #2

@philderbeast

Description

@philderbeast

When adding packages, please check subdirs.

- location:
    git: https://github.com/blockscope/hcoord.git
    commit: efee5918967a4b5309924bb6ac62c2daa56983a1
  subdirs:
  - hcoord
  - hcoord-utm
  extra-dep: true
- location:
    git: https://github.com/haskell/fgl.git
    commit: e29503775e474b7a7cd8951b6bebcf1529b888b5
  extra-dep: true
- location:
    git: https://github.com/blockscope/uom-plugin.git
    commit: c170a2df329fe8e40d13aea0b4299758d5079bda
  subdirs:
  - uom-plugin
  extra-dep: true
- location:
    git: https://github.com/brunjlar/stack2cabal
    commit: a8a4cdcacd697cee648af93856735f15de5987a6
  extra-dep: true

In the following image showing a file diff, the right pane is the packages section of cabal.project generated with stack2cabal. It does not have paths. I've corrected this problem with the file shown in the left pane to include the paths taken from the stack.yaml file above.

stack2cabal-paths

To reproduce, working off flare-timing at revision 68e62b;

> git clone https://github.com/BlockScope/flare-timing.git
> cd flare-timing
> git reset --hard 68e62b236ca4e7207e559eeb5aec7bb69f44cc6e
> stack install stack2cabal
> mv cabal.project __cabal.project
> stack exec stack2cabal .
creating cabal config for project folder '.'
writing cabal.project
DEPRECATED: Use ls dependencies instead. Will be removed in next major version.
done: writing cabal.project
...
done: creating cabal config for project folder '.'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions