https://bugs.kde.org/show_bug.cgi?id=403492
--- Comment #7 from Lonnie <k...@startport.com> --- 1) Transparency - Allow the end user to know what package is being installed (and its source) 2) Building an apt install list. I personally document each package name I install into an alphabetical list that starts off "sudo apt install . . .". When I set up new computer, I enter one command and install every single package I've ever installed and wanted to keep. With Discover, I cannot document the package name as desired. 3) Building a snap install list. Like #2, I document each snap package I install and keep, so that upon a new installation I'm one snap install command away from installing everything I want, with no worry about forgetting anything. Here's how I currently use Discover: I use it to find a piece of software that I didn't know existed, but I never allow it to install the software it finds for me, because it will not reveal the package name it is installing and I therefore cannot document that information I need for automation! Instead I research the internet each time, or do some type of apt search command until I find out what the package name is. Then I install it using apt instead of discover. If Discover would simply reveal the package name, I'd let it do the installing and I'd copy and paste that package name into my documentation before doing so. Discover must know the source and package name before it can install a package! Why hide this from users like me that definitely want to see it every single time they install something? Users who don't want to see the package name won't even notice it is there. It is typically a fairly short string. It takes up very little space. It is important to some people. It is little bother to the people that don't find it important! This is a simple and practical request. -- You are receiving this mail because: You are watching all bug changes.
