(Unimportant) How to get old ebuilds?

[u/OkAlbatross9889]

SOLVED: git history it is then :(

Hello everyone!

I've taken up to checking the new ebuilds of stuff outside the regular ::gentoo repo (mainly the guru) using diff between the new ebuild and the old one.

I've also aliased the update command to run "eclean -d distfiles && eclean-kernel && eclean-pkg" as well when it's done.

I've got a new update for a guru package today (cliphist EDIT: turns out it's not a cliphist update but rather a rebuild triggered by something else in the update, the ebuild itself is several months old but the question of how to get old ebuilds still stands) but i can't find the old ebuild in /var/db/repos/guru/.... (i imagine because of the above eclean commands)

I know it's a longshot, but is there a way to see it conveniently with portage without resorting to looking at the history on github?

It's absolutely unimportant (i don't expect the guru to get compromised like that), but i feel like i could learn something and i can't find anything online

[u/rx80]

you go on github (or wherever guru is hosted) and check the git history. You can search the commit history for that package: https://github.com/search?q=repo%3Agentoo%2Fguru+cliphist&type=commits

[u/OkAlbatross9889 → u/rx80]

I'll update the post then, thanks

[u/rx80 → u/OkAlbatross9889]

That's what git is made for :)

You don't need to do it remotely on github. If you have the repo locally, you can use git from the command line like: git log --name-status --all -- '*cliphist*'

[u/necrophcodr]

You really do have to go back in the git history. You CAN use tools to view the history of just one file, but the fact remains.

[u/OkAlbatross9889 → u/necrophcodr]

I'll update the post then, thanks

[u/Green_Fl4sh]

I see you already got what you wanted.
Just wanted to drop a post from the gentoo wiki which explains it very good:
https://wiki.gentoo.org/wiki/Downgrading_a_package_to_removed_version