| Summary: | Show package description on updates page | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | v4u6h4n <vaughan.m.johnston> |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | aleixpol, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Annotated screenshot | ||
|
Description
v4u6h4n
2023-05-25 00:57:42 UTC
Can you provide an annotated screenshot showing the exact page where you'd like the description to be shown, and where on the page the description should go? Created attachment 159378 [details]
Annotated screenshot
(In reply to Nate Graham from comment #1) > Can you provide an annotated screenshot showing the exact page where you'd > like the description to be shown, and where on the page the description > should go? Hey Nate :-) thanks for responding; I just added the screenshot as you requested. I'm not sure how this would work with different package managers as besides a brief stint with Arch I've only been using apt in Debian. However that said my suggestion is to add a short description directly below the package title, perhaps with a 'more info' hyperlink next to the brief description text that either expands an additional long description text, or redirects to the URL of the package. To use the package libc6 as an example (https://packages.debian.org/bullseye/libc6), it would look something like the following: [title] libc6 [short description] GNU C Library: Shared libraries [url] more info [long description] Contains the standard libraries that are used by nearly all programs on the system. This package includes shared versions of the standard C library and the standard math library, as well as many others. Seems sane, thanks. I'll see what I can do. (In reply to Nate Graham from comment #4) > Seems sane, thanks. I'll see what I can do. Thanks :-) |