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 had trouble figuring out how to tell pack to install a new release of Idris2. After poking around in the help and trying a few pack commands, I finally discovered that pack switch latest would download, build, and install the latest version (0.7.0, specifically 0.7.0-27780073c at this moment). I might have missed something in the online docs or commandline help, but I didn't find anything that made it clear that this would have the desired effect.
Is this the right way to upgrade Idris2 using pack?
If so, I suggest adding a note somewhere online or in the help docs that clarifies this. I can submit a PR if that would be helpful. I'm not sure what the best documentation strategy is.
Thanks!
The text was updated successfully, but these errors were encountered:
(Later I found notes that I wrote to myself earlier suggesting that this in fact the right way to upgrade idris2. I'm not sure where I got the idea from--maybe by the same route as described above, or maybe someone mentioned it on Discord.)
Using pack switch latest is indeed the correct way to do this. Unfortunately, this is indeed not yet properly documented. It would be great if we had a section about pack switch in the README, probably as a subsection of "Usage". PRs highly welcome.
I had trouble figuring out how to tell pack to install a new release of Idris2. After poking around in the help and trying a few pack commands, I finally discovered that
pack switch latest
would download, build, and install the latest version (0.7.0, specifically 0.7.0-27780073c at this moment). I might have missed something in the online docs or commandline help, but I didn't find anything that made it clear that this would have the desired effect.Is this the right way to upgrade Idris2 using pack?
If so, I suggest adding a note somewhere online or in the help docs that clarifies this. I can submit a PR if that would be helpful. I'm not sure what the best documentation strategy is.
Thanks!
The text was updated successfully, but these errors were encountered: