Skip to content

Conversation

@uncleDecart
Copy link
Member

In case if someone is trying to use local EVE it could lead to repo deletion

In case if someone is trying to use local EVE it could lead
to repo deletion

Signed-off-by: Pavel Abramov <uncle.decart@gmail.com>
@giggsoff
Copy link
Collaborator

giggsoff commented Feb 27, 2024

In that case we will not able to clean current context completely. ./eden clean --current-context will leave the directory with images unconditionally.
Can we use something more precisely, for e.g. delete dist/CONTEXT-images (assuming that user-pointed image is outside of dist) or use some flag (to keep image)? Probably the easiest option is to check if imagesDist is sub-directory of eveDist and if not, keep.

@OhmSpectator
Copy link
Member

This code has just completely removed my ~/projects, with all the projects inside (tens of them). I demand this code to be eliminated!!! (Well, if the code is fixed and no one can get the same, I'm also happy))

@uncleDecart
Copy link
Member Author

@giggsoff , when you want to run EVE locally and you point to an image (or a folder in our case, because I didn't remember) and then you do make clean it'll delete the directory, quite cruel behaviour. Maybe we can delete it only if path to EVE is not specified

@giggsoff
Copy link
Collaborator

@giggsoff , when you want to run EVE locally and you point to an image (or a folder in our case, because I didn't remember) and then you do make clean it'll delete the directory, quite cruel behaviour. Maybe we can delete it only if path to EVE is not specified

Current logic is to fill options by default, including EVE path. It is not easy to check if user override it manually.
As I mentioned, we can try to delete dist/CONTEXT-images as a path where eden-generated images stored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants