Skip to content
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

Umake should safely remove all the packages it installed #192

Open
ghost opened this issue Nov 18, 2015 · 3 comments
Open

Umake should safely remove all the packages it installed #192

ghost opened this issue Nov 18, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Nov 18, 2015

When I use the "-- remove" argument it does not remove all the packages that were installed. It would be good if "umake -r" also removes the redundant packages that it installed.

@didrocks
Copy link
Member

Thanks for opening this bug report and help pushing Ubuntu Make better!

This is indeed a hard problem, as we don't have any idea if you installed those packages automatically (through Ubuntu Make) or manually, yourself. All packages are mark as being "manually installed" so that apt-get autoremove doesn't purge them automatically. So now, let's say we remove them unconditionally. What ensure that you didn't install openjdk for instance, before installing any jetbrains IDE? What ensure that you didn't install (manually) another IDE relying on openjdk after installing your first with Ubuntu Make? Removing packages at those conditions can broke other installation.

The only "smart" way would be to generate a virtual package with the dependencies for each framework, and only installing this one on your machine, then removing it + autoremove on --remove. The issue then is that you can't have non root installation ever, even if all your dependencies are already installed, which removes one of the goal of Ubuntu Make.

On the long term, we want to implement something like described in bug #13. I guess this is a better path forward, but I'm opened to any suggestion to fix this.

@ghost
Copy link
Author

ghost commented Nov 21, 2015

@didrocks Thanks a lot for the detailed explanation. It makes sense. I am happy to close this bug.

@didrocks
Copy link
Member

Let's keep it, marked it as "question" then, as a reference :)

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

No branches or pull requests

1 participant