STEPS TO REPRODUCE 1. install any software with several dependencies (audacity audio editor, for example) 2. 3. OBSERVED RESULT Discover does not ask for confirmation to install the dependencies. It only asks for the password and starts to install all the packages immediately. EXPECTED RESULT Discover must request confirmation to install the dependencies, as it requested until some releases ago. SOFTWARE/OS VERSIONS KDE neon Developer Edition KDE Plasma: 5.14.80 KDE Frameworks: 5.53.0 Qt: 5.11.2
Why? The app can't be installed without its dependencies. If you want the app, you need to install the dependencies. Allowing you to install an app but then deny installing the dependencies makes no sense; it would be like buying a car and being asked if you want the wheels too. Since it won't work without the wheels, of course you want them!
Some time ago discover installed Gnome sections on my system together some app. Now my login manager has "Gnome" and "Gnome on X11" sessions and I can't remove Gnome sections completelly because many other packages would be removed together. If Discover had warned me that packages related to gnome sessions would be installed along with the software I wanted, I would not have proceeded. Discover should show which dependecies will install, so the user can decide if want or not to proceed.
The dependencies are already available on the app page if you want to look at them. I think the challenge here is separating benign dependencies from unwanted dependencies. In your case case GNOEME's GDM was an unwanted dependency, but how could Discover know that? I guess it probably could warn for GNOME dependencies, but that might get annoying because of you're installing Nautilus, then of course you want GNOME dependencies! Can you tell which app pulled in GDM? This sounds like it's more of a packaging bug than anything else.