Rich Freeman <rich0 <at> gentoo.org> writes: > > On Fri, Aug 28, 2015 at 9:19 AM, walt <w41ter <at> gmail.com> wrote: > > > > Note that /usr/portage/sys-libs/ncurses/Changelog was last updated on > > April 6, several months ago. > > > > Rhetorical question: what is the purpose of a Changelog? > > Gentoo is no longer maintaining the old Changelog files. The source > of all change logs going forward is in git: > > I believe there is interest in creating the old-format Changelogs for > the rsync servers. They won't be present in the git repository, since > they're just redundant extra data to sync. > > > > > Who last updated ncurses, and why? > > git whatchanged /usr/portage/sys-libs/ncurses > /tmp/log.txt > > See the attachment. You can ask git for full diffs as well fairly > easily, or show them for individual commits or whatever. Then github > or gentoo's git viewer can show you it in a pretty picture.
Hmmm. Changelogs are easy to view (less) and all quickly available on your system, should your issues with a particular ebuild coincide with network issues (cheap/sorry ISP for example). I use them extensively, now that I know of quite a few devs, read the gentoo-dev list and hack around the various ebuilds myself. It there an easy, automated way to have this inforation on my system(s) without extra keystrokes? I have become critically dependant on Changelogs to ferret out quite a few issues, so some suggestions on automating (via git) those Changelogs (not attached to the file name but certainly the concurrent data) would be keenly appreciated. I do not want to have to do what you suggest above, on a per package basis. I want all of the former Changelog data and automated in the background. So advise as to pathways or just waiting patiently as it is in somebody's todo list, would be greatly appreciated? Surely, I'm not asking too much? Explain? regards, James
