Indeed, we need to document the command correctly and list the packages to uninstall
I don’t think that to drop the delete button is a good idea. Nethserver claims to be easy to handle as it’s biggest advantage. To be able to install a package with a few clicks, but you can’t get rid of it without CLI? IMO bad manner. For those who just want to disable the installed package and don’t care about fragments that will remain it is good the way it is. And I think there are some of them.
Maybe an addtional notice, that for a full remove you have to go to CLI is an option.
Something like: “Please be aware, that this option only remove the neth-package. If you want to do a full remove, please reffer to the deinstallation notes in the wiki.”
I wouldn’t remove that button! Yes, as @giacomo said in the other topic, the Enterprise version does not have it, but the Enterprise version has also the config backup on cloud and factory reset in embedded systems: reinstalling from scratch and restoring the configuration is available out of the box
Documenting the right packages to remove is difficult: information must be consistent. I’d prefer trying to fix the group compositions and RPM dependencies, so that removals are not disruptive.
I consider such removals as bugs and they should be fixed, if possible.
The software center is a huge piece of code, but the signal won’t be good to remove the uninstall button IMHO.
If you have a bug, please correct it, it sounds simple
I totally agree…
The delete button is clear… And the guy who access the Netserver webgui is a sysadmin or at least an advanced user… not a children.
sure…but the list of deleted rpm must be clear, the removal of dependencies must be the same like with the CLI, and of course when you remove nethserver-mysql, mysql itself should be removed (for example) and unfortunately a lot of nethserver-* rpm of course.
The current behaviour just does not look consistent.
The nethserver-webproxy example can be installed and it installs squid etc… But when you remove it, nethserver-nextcloud is removed too. This is highly unwanted behavior and has nothing to do with being a sysadmin or not.
Perhaps doing it makes little sense. What does that involve?
Does the behaviour is the same with the cli ?
@stephdl: ermmm dunno shrucks
I must test this. If it is doing the same in webinterface and cli, then still IMO it is a bad thing that by removing a proxy, nextcloud gets removed too…
I agree: it doesn’t look consistent but it is
Yes it does.
This is how yum groups work.
Now I see it was a bad design decision to use yum groups as software module, my bad.
I don’t any viable alternative right now.
I bet this is now fixed
Was on the breach to open an topic it is strange the dependency’s of a nethserver-module are not removed.
And after reading this, IMHO it is still strange
I’ve just encountered this behavior with WebTop, and IMO, it’s very badly broken. If the software center is going to allow us to install software in a point-and-click manner, it likewise needs to allow us to remove it, safely and completely, in a point-and-click manner. But as noted up-thread, that’s not at all what it does. When I try to remove WebTop, for example, it doesn’t (say it’s going to) remove any of the binaries, or Java, or anything like that, but it does try to remove the mail server and everything else that acts as a webmail client.
I can run
yum remove nethserver-webtop5, of course. That should remove all the templating, redirects, etc., so it doesn’t interfere with the rest of my server–but it doesn’t do anything to remove the bloatware that is WebTop from my system (sorry, not very impressed with WebTop at the moment).
Software installation can’t be an irreversible process. I agree completely with @dnutan about the expected behavior–there has to be a way to make it behave as expected.