Created attachment 118316 [details] screenshot Please add list of files for installed package into the package page. By "package page" I mean the screen seen on the attached screenshot. SOFTWARE/OS VERSIONS Операционная система: Fedora 29 Версия KDE Plasma: 5.14.4 Версия Qt: 5.11.3 Версия KDE Frameworks: 5.54.0 Версия ядра: 4.20.4-200.fc29.x86_64 Архитектура: 64-битная Процессоры: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Память: 15,4 ГиБ ОЗУ
What's the usecase?
(In reply to Aleix Pol from comment #1) > What's the usecase? Well, to check where opencv headers are installed on my computer. Now I understand that Discover is not an experts application, thus this must be out of its scope. May be better to add a button "Show in KPackageKit" (or in whatever package manager is installed).
(In reply to Aleix Pol from comment #1) > What's the usecase? I always thought so, and with such a name, I believe Discover should give access to all informations about a package, and files list is quite a basic one. There are many situations in the life of a Linux user where she'll have to look for this, and the natural place to go find it must be software manager. Going further, I believe offering access to man pages and links to documentation would be an big plus. All these could be added to tabs to not clutter the main "page"
> There are many situations in the life of a Linux user where she'll have to look for this What are some of them? If you're a packager or a software dev, maybe, but in those cases wouldn't a command-line program be a vastly faster and more efficient tool to use?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
> If you're a packager or a software dev, maybe, but in those cases wouldn't a command-line program be a vastly faster and more efficient tool to use? Checking where opencv headers are installed is indeed a software dev use case. However, being a software developer doesn't imply I'm familiar with CLI package management tools of a given Linux distro. For example, I had been exposed to Debian/Ubuntu environments at my job(s) over the past ~10 years, yet I don't fully understand how dpkg/apt work and can't remember relevant CLI commands, possibly because I'm more used to other distros.