-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wally should not outright nuke the Packages folder if it already exists #161
Comments
If your submodules are set up correctly you should just have to re-initialize them. This is something easier said than done to add. Modifying the Packages folder is expected during normal operation of The warning issue a similar one. It would be incredibly inconvenient to use if it warned you about changing the installed packages every time you add or remove packages. That's what you were trying to do and now it's warning you during normal operation. |
Perhaps as a sort of compromise the |
Yeah I like the idea of We can instead support this use case by allowing you to tell wally to name the packages folders differently but I'm not sure if this is a strong enough use case to push us to enable that yet. Moving submodules to another folder is easy, although I can appreciate it may be annoying. |
... or it should at least give a warning with a confirm prompt before doing so.
This causes issues if you were using the folder for submodules. They enter a state where they cannot be neither re-added or removed (unless you use the --force flag)
The text was updated successfully, but these errors were encountered: