Hacker News Reader

Comment by creer | Hacker News Reader

It's not unfair of the maintainer to only maintain the current versions. That would be fine.

Old versions (ebuilds and patches) are really not easy to find once they are gone from the portage ebuild tree. I still don't know where they live.

View on HN

Speaking as someone that maintains some old and dropped shit in my own overlay and GURU ( https://cgit.gentoo.org/repo/proj/guru.git ), the web archive and Gentoo's own git history are where I usually find old ebuilds. They are of limited use, too old and it's ancient EAPI where ebuild style used to be more complicated, most of the time it just makes sense to rewrite the ebuild in EAPI 8 if needed. The main things I'm looking for are the notes and stuff like custom initscripts that might have been written.

If a dropped package is of interest and there's a reason it shouldn't be in the tree I usually submit it to GURU. If I use it and it probably should be saved or re-added to the tree I proxy maintain it.

Thank you @Sembiance and you!

When I somehow get to an old ebuild like perhaps gentoo/www-client/chromium /chromium-118.0.5993.54.ebuild here:

https://github.com/gentoo/gentoo/blob/3fb0eea1ee35033113d7af...

how do I find which gentoo portage 'files' were live at the time? (poor example - there may have been no change in this case.)

Checkout the commit? You'll have a local copy of the tree exactly as it was at that time.

Thank you! I don't live in git and this helps! Normally under gentoo I shouldn't have to. This actual git https://github.com/gentoo/gentoo (as opposed to the gentoo browser view) plus this "checkout the commit" should get me much further. ... And probably deserve some space in the gentoo docs.

If you go to an earlier commit here, you can find earlier versions: https://github.com/gentoo/gentoo

Reply on news.ycombinator.com