Open hvr opened 6 years ago
Note that even if we don't do the check out, we'll still need to get the .cabal
file from the repo, as we need that .cabal
file to figure out things like the project name, which we'll need to figure out if we need to override something in the LTS.
Ok... that's tricky... you could use a 2-pass schema, where you'd let cabal
pre-fetch the git repos (e.g. via cabal new-build --dry --allow-newer=*:*
, and then inspect the plan.json
file from which you could easily read off the remote git repo packages and their respective pkg-ids. Maybe cabal new-fetch
could provide something tooling like stack2cabal could hook into
besides the current mode which invokes
git clone
for you,stack2cabal
ought to support mapping remote git repo deps instack2yaml
to cabal's new native support for them;Current syntax looks like so
cabal 2.4 probably won't be able to support specifying multiple subdirs in a single
source-repository-package
stanza yet.