-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Show a summary which packages exist for major distros #62
Comments
At first glance, it's data duplication. But it actually related to other things planned repology/repology-webapp#44, repology/repology-updater#562, repology/repology-updater#514 and probably more. I'm not sure how to it in an usable way yet though.
This won't be much different from the |
The rough idea is as follows: a multi-column (so it doesn't take too much vertical space) list (similar to Absent in repositories at the bottom of Versions page) with repository families the project is packaged in. Entries would be clickable, highlighting table rows for all repositories belonging to the selected family, and scrolling to the first (or main, but we'll have to set this by hand) representative of the family (e.g. Arch (and not Manjaro) for Arch family). How does that sound? This is also somewhat related to repology/repology-webapp#37. |
Currently, when the user looks at the list he can't immediately tell which packages are or aren't available. Ex. https://repology.org/project/emscripten/versions It is necessary to go through the long list, or perform textual search.
I suggest that you add the summary box in the top-right corner with the summary/aggregate information at a glance, ex:
This should be with one line for every unique packaging system, with details when many distros use the same packaging system.
I often find myself hitting Ctrl-C and typing "freebsd" to find if it is available for freebsd, etc.
This is a usability feature, it adds user convenience, and not information that wasn't previously available.
The text was updated successfully, but these errors were encountered: