Should bloop remove old projects when doing install? about bloop HOT 6 CLOSED

I personally think for now it's best to delegate this to users with rm -rf .bloop-config. I like the fact that I can incrementally update the config for one project.

from bloop.

I think it should indeed be removed. Otherwise, users can still see how bloop is trying to compile their projects if the dependencies are maintained. That's bad.

from bloop.

Yeah you're probably right, install is fast anyways so it's probably best to clean up .bloop-config to avoid staleness issues

from bloop.

Note we can still accomplish the goal in this ticket while staying incremental 😄.

from bloop.

I like the fact that I can incrementally update the config for one project.

I take back my comment, I think bloopInstall should overwrite old configurations.

from bloop.

This has been causing confusion and errors for me. Especially when upgrading bloop, some of the old files still being there caused problems because they were incompatible.

from bloop.