stack rm command

[snoyberg]

• Without arguments, lists all local GHCs and snapshots
• Takes output from previous command and deletes relevant directories
• Maybe have a --all flag?

Thoughts on this from anyone?

[snoyberg]

Can also be used to delete old GHC/Git archives (see #376, and pinging @conklech

[rvion]

Without arguments, lists all local GHCs and snapshots

do you mean: without arguments, list all local GHC and snapshots and ask the user to re-run the command with one or several of them after stack rm

Takes output from previous command and deletes relevant directories

not sure to understand

Maybe have a --all flag?

+1

[snoyberg]

Yes, that's what I meant. My idea is that the output will be something like:

Can delete:

* stack rm ghc-7.8.4
* stack rm ghc-7.10.1
* stack rm lts-2.15

Running any of those commands will delete the relevant directories

[conklech]

+1 from me, too. --all would be constructive, and ought to be mentioned alongside the installation instructions; it should be best practice to have a documented uninstallation procedure.

[radix]

I'm slightly uneasy about calling this "rm", it just doesn't seem like the right name for it. Maybe "clean" or "cleanup"?

Feel free to ignore my bikeshedding :)

[rvion]

@radix I understand it may not feel like the best name, but I think lots of people are used to this one.
I would still go for stack rm because of git rm and docker rm, that will be used by most users of stack

[conklech]

Two issues arose from #376 that are relevant here:

1. Should we give an option to delete just the GHC tarball without nuking the installation? And should stack rm ghc-7.8.4 remove or preserve the installation tarball? See Remove GHC/git tarballs after installation #376 for discussion of the rationales for each option.

2. On Windows, stack also installs its own git. That should be on the list as well.