Skip to content
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

Sort update list using semantic versioning #1331

Open
tuxayo opened this issue Feb 6, 2025 · 1 comment
Open

Sort update list using semantic versioning #1331

tuxayo opened this issue Feb 6, 2025 · 1 comment

Comments

@tuxayo
Copy link

tuxayo commented Feb 6, 2025

On the right there is the current paru output. On the left image we have an example of how could look an update list that is sorted by major update first, then minor, then patch, then package revision.
Image

There is also color showing the changed part of the version. Like in some diff formats. And it helps seeing quickly when we switch down to a lower upgrade level.
The colors could be pastel or anything else easy on the eyes, as the question of colors already came up in another ticket.

The sorting + the nice diff display is a massive help to be aware of major updates at the 1st glance and quickly skim over the sometimes very numerous revisions bump at the end of the list.
Otherwise, it's easy to miss the most important version changes among the others.

Thanks for making this cool AUR helper and pacman wrapper :D

Have you checked the readme and man page for this feature?
Yes

Have you checked previous issues for this feature?
Yes, #1317 and #1194 are adjacent but not quite.

@tuxayo tuxayo changed the title Sort update list using semantic versionning Sort update list using semantic versioning Feb 6, 2025
@rezad1393
Copy link

rezad1393 commented Feb 6, 2025

this is a good idea.
maybe first by repo (core first because that is the most based part) and then this sort.

when a user sees a list that is just same color and just sorted by name (like right now paru is) it gives some idea what packages are updated, but it could be much more informative with a color output and sorting as suggested here.

but in my opinion sort should first done by your way (semantic versioning) then by repo way so that core packages are the top no matter what.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants