How to prevent stack from downloading GHC for every new project?
up vote
0
down vote
favorite
How to prevent stack from downloading GHC for every new project?
Every time I create a new project using stack and then build or exec the codes, stack will install a new GHC for me. This is not only boring for waiting such a long time for a huge image to be downloaded (behind the GFW, xKib/s), but also a space disaster for my pity 128G SSD Macbook Pro. How can I fix this?
$ stack exec blah
Preparing to install GHC to an isolated location.
This will not interfere with any system-level installation.
ghc-8.4.4: 15.98 KiB / 220.05 MiB ( 0.01%) downloaded...^C
haskell haskell-stack
add a comment |
up vote
0
down vote
favorite
How to prevent stack from downloading GHC for every new project?
Every time I create a new project using stack and then build or exec the codes, stack will install a new GHC for me. This is not only boring for waiting such a long time for a huge image to be downloaded (behind the GFW, xKib/s), but also a space disaster for my pity 128G SSD Macbook Pro. How can I fix this?
$ stack exec blah
Preparing to install GHC to an isolated location.
This will not interfere with any system-level installation.
ghc-8.4.4: 15.98 KiB / 220.05 MiB ( 0.01%) downloaded...^C
haskell haskell-stack
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How to prevent stack from downloading GHC for every new project?
Every time I create a new project using stack and then build or exec the codes, stack will install a new GHC for me. This is not only boring for waiting such a long time for a huge image to be downloaded (behind the GFW, xKib/s), but also a space disaster for my pity 128G SSD Macbook Pro. How can I fix this?
$ stack exec blah
Preparing to install GHC to an isolated location.
This will not interfere with any system-level installation.
ghc-8.4.4: 15.98 KiB / 220.05 MiB ( 0.01%) downloaded...^C
haskell haskell-stack
How to prevent stack from downloading GHC for every new project?
Every time I create a new project using stack and then build or exec the codes, stack will install a new GHC for me. This is not only boring for waiting such a long time for a huge image to be downloaded (behind the GFW, xKib/s), but also a space disaster for my pity 128G SSD Macbook Pro. How can I fix this?
$ stack exec blah
Preparing to install GHC to an isolated location.
This will not interfere with any system-level installation.
ghc-8.4.4: 15.98 KiB / 220.05 MiB ( 0.01%) downloaded...^C
haskell haskell-stack
haskell haskell-stack
asked Nov 20 at 3:07
cmal
552316
552316
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
4
down vote
accepted
Stack only installs a new ghc if the stack.yaml you are using requires some ghc version that you do not yet have installed via stack. Once stack has installed ghc-8.4.4, for example, it will not reinstall this version of ghc.
I would presume the solution, then, is to make sure you are using the same resolver for all of your projects, so that stack only installs the one ghc version.
It might be worth it mentioning the--resolver
option explicitly,
– duplode
Nov 20 at 3:57
add a comment |
up vote
0
down vote
Just find $HOME/.stack.yaml
and add:
# Turn on system GHC
system-ghc: true
and run the same command again.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
Stack only installs a new ghc if the stack.yaml you are using requires some ghc version that you do not yet have installed via stack. Once stack has installed ghc-8.4.4, for example, it will not reinstall this version of ghc.
I would presume the solution, then, is to make sure you are using the same resolver for all of your projects, so that stack only installs the one ghc version.
It might be worth it mentioning the--resolver
option explicitly,
– duplode
Nov 20 at 3:57
add a comment |
up vote
4
down vote
accepted
Stack only installs a new ghc if the stack.yaml you are using requires some ghc version that you do not yet have installed via stack. Once stack has installed ghc-8.4.4, for example, it will not reinstall this version of ghc.
I would presume the solution, then, is to make sure you are using the same resolver for all of your projects, so that stack only installs the one ghc version.
It might be worth it mentioning the--resolver
option explicitly,
– duplode
Nov 20 at 3:57
add a comment |
up vote
4
down vote
accepted
up vote
4
down vote
accepted
Stack only installs a new ghc if the stack.yaml you are using requires some ghc version that you do not yet have installed via stack. Once stack has installed ghc-8.4.4, for example, it will not reinstall this version of ghc.
I would presume the solution, then, is to make sure you are using the same resolver for all of your projects, so that stack only installs the one ghc version.
Stack only installs a new ghc if the stack.yaml you are using requires some ghc version that you do not yet have installed via stack. Once stack has installed ghc-8.4.4, for example, it will not reinstall this version of ghc.
I would presume the solution, then, is to make sure you are using the same resolver for all of your projects, so that stack only installs the one ghc version.
answered Nov 20 at 3:46
Dan Burton
36.9k2096179
36.9k2096179
It might be worth it mentioning the--resolver
option explicitly,
– duplode
Nov 20 at 3:57
add a comment |
It might be worth it mentioning the--resolver
option explicitly,
– duplode
Nov 20 at 3:57
It might be worth it mentioning the
--resolver
option explicitly,– duplode
Nov 20 at 3:57
It might be worth it mentioning the
--resolver
option explicitly,– duplode
Nov 20 at 3:57
add a comment |
up vote
0
down vote
Just find $HOME/.stack.yaml
and add:
# Turn on system GHC
system-ghc: true
and run the same command again.
add a comment |
up vote
0
down vote
Just find $HOME/.stack.yaml
and add:
# Turn on system GHC
system-ghc: true
and run the same command again.
add a comment |
up vote
0
down vote
up vote
0
down vote
Just find $HOME/.stack.yaml
and add:
# Turn on system GHC
system-ghc: true
and run the same command again.
Just find $HOME/.stack.yaml
and add:
# Turn on system GHC
system-ghc: true
and run the same command again.
answered Nov 20 at 3:21
cmal
552316
552316
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385640%2fhow-to-prevent-stack-from-downloading-ghc-for-every-new-project%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown