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
In order to speed up building the Idris compiler, pack tries to use an already installed version of Idris instead of bootstrapping the hole thing. This works reasonably well with pack switch latest, but fails, if people edit their pack.toml files manually unless they specifically use --bootstrap as a command line option. See also the discussion in #220 .
I'm sure we can be smarter than that.
The text was updated successfully, but these errors were encountered:
That's strange. I set alternative Idris version in local pack.toml files many times, never passed the --bootstrap option and still never ran into this problem. How can this be?
That's strange. I set alternative Idris version in local pack.toml files many times, never passed the --bootstrap option and still never ran into this problem. How can this be?
Do you have bootstrap set to true in one of your pack.toml files?
That's strange. I set alternative Idris version in local pack.toml files many times, never passed the --bootstrap option and still never ran into this problem. How can this be?
Do you have bootstrap set to true in one of your pack.toml files?
No, it is set to false in ~/.pack/user/pack.toml and it is not reset in local ones.
In order to speed up building the Idris compiler, pack tries to use an already installed version of Idris instead of bootstrapping the hole thing. This works reasonably well with
pack switch latest
, but fails, if people edit theirpack.toml
files manually unless they specifically use--bootstrap
as a command line option. See also the discussion in #220 .I'm sure we can be smarter than that.
The text was updated successfully, but these errors were encountered: