Seeing the changelog in eopkg

brent

I actually rtm (man eopkg) in order to prepare for the 4.8 change of deprecating the SC.
I will have more questions. One of the things I really value is the changelog. For instance:

$ eopkg blame alacritty
Name: alacritty, version: 0.15.1, release: 35
Package Maintainer: Muhammad mal@hotmail.com
Release Updater: Muhammad i mal@hotmail.com
Update Date: 2025-06-14

alacritty: Housekeeping

Summary

Use cargo macro instead of make
Add more comments

QUESTIONS:
1) is eopkg blame the right way to see the changelog?
2) there is no--verbose flag in eopkg, is there a way to get it more verbose? (maybe it doesn't need to be)
3) is there a way to see the last 2-3 logs in a single command, like in the SC picture at top?

edit: cropped emails/names

Harvey

Yes that is the only way from the command line to my knowledge but the new software center replacements still show this as I have stated before.

gnome-software
{gnome-software?}

discover
{discover?}

brent

Harvey very nice. I like very much the site links in Discover. (Am I the only one that nerds out and reads changelogs and the links in them?)
thanks for the info!

Harvey

Since that only appears for updates before they are installed to my knowledge and seeing you seem to like it that much. You can go to our package recipe repo https://github.com/getsolus/packages You will be able to read about updates before they even land in shannon (stable).

For example, navigate to the directory for alacritty and you can see every commit ever made for that package in the Solus repository. https://github.com/getsolus/packages/commits/main/packages/a/alacritty click the ... on each commit to read the commit message which is where the changelog comes from in those screenshots above.

brent

Harvey this will put me on the road to OCD, looking forward!

-for some packages, its evolution is interesting. the more I read the minutiae the more I think I understand what's underneath a program. and that matters.

as always, Harvey thanks for the depth

Harvey

I was curious and looked at command line args more.

eopkg blame alacritty would get you the installed version.

You can take the release number shown for that and work backwards for releases.
Name: alacritty, version: 0.15.1, release: 35

So for the previous update:
eopkg blame -r 34 alacritty

or you can view the last few updates with the stupidly named -a flag because it doesn't actually show all.
eopkg blame -a alacritty

brent

Harvey
I tried these that's pretty cool to do in eopkg.
also tried eopkg blame -r 32 33 34 alacritty thinking I could see last three versions but it just defaults to the first number (32)

eopkg blame -a alacritty ---this actually went back to 26 which is interesting--that's about what I'm looking for.

Staudey

Harvey or you can view the last few updates with the stupidly named -a flag because it doesn't actually show all.

Well, it shows "all" in the sense of showing all the history that it is contained within the package metadata 😄
The rest gets cut off, or rather not produced in the first place, on package creation (because the max history size is set to 10 in ypkg)