You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it'd be nice to be able to inline the resolver as an object in stack.yaml, since I suspect that there'll be strong ties between the local package sets and the snapshot/resolver (e.g., needing to change ghc-options on old LTSes, some local packages known not to work on some GHC versions). Also, the common case is going to be one stack.yaml and one resolver.
So I'd like something like this:
stack.yaml:
resolver:
resolver: lts-9.0
packages: [foo-0.1]
packages: [foo, bar, baz]
The text was updated successfully, but these errors were encountered:
Hmm, could do this. It'd probably be best just to finally implement #3330 ! I would prefer to do that rather than making resolver more complex.
So thanks for the idea, but I am going to close this as wontfix. Perhaps I've misunderstood or others would particularly like this idea. In that case, speak up and maybe this can be reopened.
With the upcoming release, now we can define our own custom snapshots, e.g.:
I think it'd be nice to be able to inline the resolver as an object in stack.yaml, since I suspect that there'll be strong ties between the local package sets and the snapshot/resolver (e.g., needing to change ghc-options on old LTSes, some local packages known not to work on some GHC versions). Also, the common case is going to be one stack.yaml and one resolver.
So I'd like something like this:
The text was updated successfully, but these errors were encountered: